Docs for upgrading daemon

daemon/upgrade/0.5_to_0.6.md

@@ -0,0 +1,61 @@
+# Upgrading 0.5.X to 0.6.0
+
+[[toc]]
+
+::: warning Server Restart Required
+Your servers will need to be restarted after upgrading the daemon in order to see the expected log output in the Panel.
+:::
+
+## Breaking Changes
+This release introduces a few breaking changes to how the Daemon operates, but maintains compatability with `v0.7.X` of
+the Panel, so you don't need to worry about updating the Panel.
+
+Of notable change in this release is that we've switched from using custom logging functionality to using Docker logging
+functionality. This allows us to better output events that happen before we can attach to the container, centralizes logic,
+and allows Docker to manage the logs (which it does very well). Now, when your server refuses to boot, instead of seeing
+an unhelpful "Server has crashed" message with nothing before it, you'll see _everything_ that happened in the container
+leading up to that point, assuming things were output.
+
+## Download Files
+To upgrade from v0.5.X first switch the directory where you installed your Daemon. If you followed the installation
+guide your Daemon is most likely located in `/srv/daemon`. Then, download and unpack the archive using the
+command below.
+
+::: danger
+Stop your Daemon process before continuing in order to avoid any issues and ensure everything updates as expected.
+:::
+
+``` bash
+curl -L https://github.com/pterodactyl/daemon/releases/download/v0.6.0/daemon.tar.gz | tar --strip-components=1 -xzv
+```
+
+Then, update the core dependencies for the Daemon with the following command.
+
+``` bash
+npm update --only=production
+```
+
+### Start the Daemon
+Finally, start your daemon up, most likely with the command below.
+
+``` bash
+systemctl start wings
+```
+
+## Rebuild Containers
+Because of some changes we made behind the scenes when it comes to displaying server output you'll need to rebuild and
+restart all of your servers. The rebuild step is required, the restart step is optional, but highly recommended otherwise
+you will not be able to see any console output.
+
+Run the following commands _from the Panel server_ in order to perform a mass rebuild and restart. Replace `###` with the
+ID of the node you just upgraded, or remove the `--node` flag entirely to rebuild on all nodes.
+
+``` bash
+php artisan p:server:rebuild --node=###
+```
+
+Then, restart all of the servers using the following command, or by manually restarting them one at a time in the Panel.
+
+``` bash
+php artisan p:server:restart --node=###
+```

daemon/upgrading.md

@@ -3,3 +3,4 @@
 ## Version Specific Guides
 * [0.4.X to 0.5.X](upgrade/0.4_to_0.5.md)
 * [0.5.X series](upgrade/0.5.md) <Badge text="current" vertical="middle"/>
+* [0.5.X to 0.6.x](upgrade/0.5_to_0.6.md) <Badge text="beta" vertical="middle" type="warn"/>

package.json

@@ -2,7 +2,7 @@
   "dependencies": {
     "jquery": "^3.3.1",
     "slick-carousel": "^1.8.1",
-    "vuepress": "^0.13.0"
+    "vuepress": "^0.13.1"
   },
   "scripts": {
     "build": "./node_modules/vuepress/bin/vuepress.js build",

yarn.lock

@@ -6653,9 +6653,9 @@ vuepress-html-webpack-plugin@^3.2.0:
     toposort "^1.0.0"
     util.promisify "1.0.0"
 
-vuepress@^0.13.0:
-  version "0.13.0"
-  resolved "https://registry.yarnpkg.com/vuepress/-/vuepress-0.13.0.tgz#7959feeb8c4bbd1cd96238383566182419576d5d"
+vuepress@^0.13.1:
+  version "0.13.1"
+  resolved "https://registry.yarnpkg.com/vuepress/-/vuepress-0.13.1.tgz#73178d58f5b0660f7dbbdd4172b0170051eb1ea9"
   dependencies:
     "@babel/core" "7.0.0-beta.47"
     "@vue/babel-preset-app" "3.0.0-beta.11"