Merge pull request #206 from synocx/patch-4

Add upgrading page for 1. 0
This commit is contained in:
Jakob 2020-04-28 09:55:23 +02:00 committed by GitHub
commit b9acbf3cef
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 30 additions and 2 deletions

View File

@ -146,7 +146,8 @@ module.exports = {
status: 'beta',
children: [
'/getting_started',
'/webserver_configuration'
'/webserver_configuration',
'/upgrading'
]
}
]

View File

@ -26,4 +26,4 @@ php artisan queue:restart
* [0.6.X to 0.7.17](/panel/upgrade/0.6_to_0.7.md)
* [0.7.X series](/panel/upgrade/0.7.md) <Badge text="current" vertical="middle"/>
* [1.0.X series](/panel/upgrade/1.0.md) <Badge text="alpha release" vertical="middle"/>
* [0.7.17 to 1.0.X](/panel/upgrade/0.7_to_1.0.md) <Badge text="alpha release" vertical="middle"/>

27
panel/1.0/upgrading.md Normal file
View File

@ -0,0 +1,27 @@
# Upgrading
Upgrading the Panel is a relatively simple process. Below you will find a list of articles that will walk you through
the upgrade process for each version of the software.
## Maintenance Mode
Whenever you are performing an upgrade you should be sure to place your Panel into maintenance mode. This will prevent
users from encountering unexpected errors and ensure everything can be upgraded before users being encountering
potentially new features.
``` bash
# Put the Panel into maintenance mode and deny user access
php artisan down
# Bring the Panel back up to receive connections.
php artisan up
```
## Restarting Queue Workers
After _every_ update you should restart the queue worker to ensure that the new code is loaded in and used.
``` bash
php artisan queue:restart
```
## Version Specific Guides
* [1.0.X series](/panel/upgrade/1.0.md) <Badge text="alpha release" vertical="middle"/>