Updating process

Home.md

@@ -4,6 +4,7 @@
 - [[FAQ]]
 
 ### Additional Configuration ###
+- [[Updating]]
 - [[SSL]]
 - [[Reverse Proxy]]
 - [[Release Branches]]

Updating.md

@@ -0,0 +1,31 @@
+## General ##
+
+**Branch** - You can change the branch NzbDrone will use to update, see [[Release Branches]] for more information.
+
+## Windows ##
+
+Windows has automatic updates without making any changes.
+
+## Linux/OS X ##
+
+Both Linux and OS X now have the ability to update directly from the UI or automatically, but it is not enabled by default.
+
+### Options ###
+**Automatic** - Enable automatic updating, please test the update process manually to ensure it will work for your setup before enabling
+
+**Mechanism**
+    - **Built-in** - Use NzbDrone's own updater
+    - **Script** - Use a custom external script to update NzbDrone, it will need to take care of stopping and starting drone during the update process
+
+**Script** - Visible only when *Mechanism* is set to *Script* - Path to update script
+
+
+### Update Process ###
+NzbDrone will download the update file, verify its integrity and extract it to a temporary location and call the chosen method. The update process will be be run under the same user that NzbDrone is run under, it will need permissions to update the NzbDrone files as well as stop/start NzbDrone.
+
+#### Built-in ####
+The built-in method will backup NzbDrone files and settings, stop NzbDrone, update the installation and Start NzbDrone, if your system will not handle the stopping of NzbDrone and will attempt to restart it automatically it may be best to use a script instead. In the event of failure the previous version of NzbDrone will be restarted.
+
+
+#### Script ####
+The script should handle the the same as the built-in updater, if you need to handle stopping and starting services (upstart/launchd/etc) you will need to do that here.