diff --git a/.vuepress/config.js b/.vuepress/config.js index 57bfdb1b..43421312 100644 --- a/.vuepress/config.js +++ b/.vuepress/config.js @@ -146,7 +146,8 @@ module.exports = { status: 'beta', children: [ '/getting_started', - '/webserver_configuration' + '/webserver_configuration', + '/upgrading' ] } ] diff --git a/panel/0.7/upgrading.md b/panel/0.7/upgrading.md index 20a8e1df..18c8575f 100644 --- a/panel/0.7/upgrading.md +++ b/panel/0.7/upgrading.md @@ -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) -* [1.0.X series](/panel/upgrade/1.0.md) +* [0.7.17 to 1.0.X](/panel/upgrade/0.7_to_1.0.md) diff --git a/panel/0.7/upgrade/1.0.md b/panel/1.0/upgrade/1.0.md similarity index 100% rename from panel/0.7/upgrade/1.0.md rename to panel/1.0/upgrade/1.0.md diff --git a/panel/1.0/upgrading.md b/panel/1.0/upgrading.md new file mode 100644 index 00000000..c9d089e5 --- /dev/null +++ b/panel/1.0/upgrading.md @@ -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) \ No newline at end of file