Merge pull request pterodactyl#2 from pterodactyl/develop

Keep up to date

Author: stanjg

.env.example

@@ -6,6 +6,7 @@ APP_TIMEZONE=America/New_York
 APP_CLEAR_TASKLOG=720
 APP_DELETE_MINUTES=10
 APP_ENVIRONMENT_ONLY=true
+LOG_CHANNEL=daily
 
 DB_HOST=127.0.0.1
 DB_PORT=3306

.env.travis

@@ -5,10 +5,10 @@ APP_THEME=pterodactyl
 APP_TIMEZONE=UTC
 APP_URL=http://localhost/
 
-DB_HOST=127.0.0.1
-DB_DATABASE=travis
-DB_USERNAME=root
-DB_PASSWORD=""
+TESTING_DB_HOST=127.0.0.1
+TESTING_DB_DATABASE=travis
+TESTING_DB_USERNAME=root
+TESTING_DB_PASSWORD=""
 
 CACHE_DRIVER=array
 SESSION_DRIVER=array

.github/ISSUE_TEMPLATE.md

@@ -1,6 +1,8 @@
 <!---
 Please take a little time to submit a good issue. It makes our life easier and the issue will be resolved quicker.
 
+!!! GitHub is NOT the place for difficulties setting up this software. Please use it for bugs and feature requests only. If you have issues setting up the panel or the daemon visit our Discord server: https://pterodactyl.io/discord
+
 If you are submitting a feature request please remove everything in here. Then give a detailed explanation what you want to have implemented and why that would be a good addition.
 
 Please also try to give the issue a good title: It should summarize your issue in a few words and help us see what the issue is about in a glance. Things like "Panel is not working" do not help.

.travis.yml

@@ -14,9 +14,9 @@ before_script:
   - echo 'opcache.enable_cli=1' >> ~/.phpenv/versions/$(phpenv version-name)/etc/conf.d/travis.ini
   - cp .env.travis .env
   - travis_retry composer install --no-interaction --prefer-dist --no-suggest
-  - php artisan migrate --seed
 script:
-  - vendor/bin/phpunit --coverage-clover coverage.xml
+  - vendor/bin/phpunit --bootstrap vendor/autoload.php --coverage-clover coverage.xml tests/Unit
+  - vendor/bin/phpunit tests/Integration
 notifications:
   email: false
   webhooks:

CHANGELOG.md

@@ -4,14 +4,14 @@ We're glad you want to help us out and make this panel the best that it can be!
 ### Project Branches
 This section mainly applies to those with read/write access to our repositories, but can be helpful for others.
 
-The `develop` branch should always be in a runnable state, and not contain any major breaking features. For the most part this means you will need to create `feature/` branches in order to add new functionality, or change how things work. When making a feature branch, if it is referencing something in the issue tracker, please title the branch `feature/PTDL-###` where `###` is the issue number.
+The `develop` branch should always be in a runnable state, and not contain any major breaking features. For the most part, this means you will need to create `feature/` branches in order to add new functionality or change how things work. When making a feature branch, if it is referencing something in the issue tracker, please title the branch `feature/PTDL-###` where `###` is the issue number.
 
-Moving forward all commits from contributors should be in the form of a PR, unless it is something we have previous discussed as being able to be pushed right into `develop`.
+Moving forward all commits from contributors should be in the form of a PR, unless it is something we have previously discussed as being able to be pushed right into `develop`.
 
-All new code should contain unit tests at minimum (where applicable). There is a lot of un-covered code currently, so as you are doing things please be looking for places that you can write tests.
+All new code should contain unit tests at a minimum (where applicable). There is a lot of uncovered code currently, so as you are doing things please be looking for places that you can write tests.
 
 ### Update the CHANGELOG
-When adding something that is new, fixed, changed, or security related for the next release you should be adding a note to the CHANGELOG. If something is changing within the same version (i.e. fixing a bug introduced but not released) it should _not_ go into the CHANGELOG.
+When adding something that is new, fixed, changed, or security-related for the next release you should be adding a note to the CHANGELOG. If something is changing within the same version (i.e. fixing a bug introduced but not released) it should _not_ go into the CHANGELOG.
 
 ### Code Guidelines
 We are a `PSR-4` and `PSR-0` compliant project, so please follow those guidelines at a minimum. In addition, StyleCI runs on all of our code to ensure the formatting is standardized across everything. When a PR is made StyleCI will analyze your code and make a pull to that branch if necessary to fix any formatting issues. This project also ships with a PHP-CS configuration file and you are welcome to configure your local environment to make use of that.
@@ -32,13 +32,13 @@ class ProcessScheduleService
 ```
 
 ### Responsible Disclosure
-This is a fairly in-depth project, and makes use of a lot of parts. We strive to keep everything as secure as possible, and welcome you to take a look into it yourself. We do ask that you be considerate of others who are using the software and not publicly disclose security issues without contacting us first by email.
+This is a fairly in-depth project and makes use of a lot of parts. We strive to keep everything as secure as possible and welcome you to take a look at the code provided in this project yourself. We do ask that you be considerate of others who are using the software and not publicly disclose security issues without contacting us first by email.
 
 We'll make a deal with you: if you contact us by email and we fail to respond to you within a week you are welcome to publicly disclose whatever issue you have found. We understand how frustrating it is when you find something big and no one will respond to you. This holds us to a standard of providing prompt attention to any issues that arise and keeping this community safe.
 
 If you've found what you believe is a security issue please email us at `support@pterodactyl.io`.
 
 ### Where to find Us
-You can find us in a couple places online. First and foremost, we're active right here on Github. If you encounter a bug or other problem open an issue on here for us to take a look at it. We also accept feature requests here as well.
+You can find us in a couple places online. First and foremost, we're active right here on Github. If you encounter a bug or other problems, open an issue on here for us to take a look at it. We also accept feature requests here as well.
 
 You can also find us on [Discord](https://pterodactyl.io/discord). In the event that you need to get in contact with us privately feel free to contact us at `support@pterodactyl.io`. Try not to email us with requests for support regarding the panel, we'll probably just direct you to our Discord.

CONTRIBUTING.md

@@ -58,7 +58,7 @@ class AppSettingsCommand extends Command
      * @var string
      */
     protected $signature = 'p:environment:setup
-                            {--new-salt : Wether or not to generate a new salt for Hashids.}
+                            {--new-salt : Whether or not to generate a new salt for Hashids.}
                             {--author= : The email that services created on this instance should be linked to.}
                             {--url= : The URL that this Panel is running on.}
                             {--timezone= : The timezone to use for Panel times.}

app/Console/Commands/Environment/AppSettingsCommand.php

@@ -59,6 +59,7 @@ public function __construct(ConfigRepository $config)
 
     /**
      * Handle command execution.
+     * @throws \Pterodactyl\Exceptions\PterodactylException
      */
     public function handle()
     {

app/Console/Commands/Environment/EmailSettingsCommand.php

@@ -84,7 +84,7 @@ public function handle()
             ['Host', $this->config->get("database.connections.{$driver}.host")],
             ['Port', $this->config->get("database.connections.{$driver}.port")],
             ['Database', $this->config->get("database.connections.{$driver}.database")],
-            ['Usernamne', $this->config->get("database.connections.{$driver}.username")],
+            ['Username', $this->config->get("database.connections.{$driver}.username")],
         ], 'compact');
 
         $this->output->title('Email Configuration');

app/Console/Commands/InfoCommand.php

@@ -31,8 +31,8 @@ class BulkPowerActionCommand extends Command
      */
     protected $signature = 'p:server:bulk-power
                             {action : The action to perform (start, stop, restart, kill)}
-                            {--servers= : A comma seperated list of servers.}
-                            {--nodes= : A comma seperated list of nodes.}';
+                            {--servers= : A comma separated list of servers.}
+                            {--nodes= : A comma separated list of nodes.}';
 
     /**
      * @var string