summaryrefslogtreecommitdiff
path: root/docs/administration/updating.md
diff options
context:
space:
mode:
authorAlexander Strizhakov <alex.strizhakov@gmail.com>2020-02-21 10:02:37 +0300
committerAlexander Strizhakov <alex.strizhakov@gmail.com>2020-02-21 10:02:37 +0300
commit13918cb545d583decfb728300850b307c59e2031 (patch)
tree9bf3d5f4c2e51eec87bd0cd1e8a46a6b94816bfc /docs/administration/updating.md
parentc9db0507f8d49aee9988b0b63477672f5df9c0b2 (diff)
parent292031f6dd809accbcb3a5ba59d0100d807c5d72 (diff)
downloadpleroma-13918cb545d583decfb728300850b307c59e2031.tar.gz
pleroma-13918cb545d583decfb728300850b307c59e2031.zip
Merge branch 'develop' into gun
Diffstat (limited to 'docs/administration/updating.md')
-rw-r--r--docs/administration/updating.md17
1 files changed, 17 insertions, 0 deletions
diff --git a/docs/administration/updating.md b/docs/administration/updating.md
index 84e6ef18d..2a08dac1f 100644
--- a/docs/administration/updating.md
+++ b/docs/administration/updating.md
@@ -1,4 +1,21 @@
# Updating your instance
+
+You should **always check the release notes/changelog** in case there are config deprecations, special update special update steps, etc.
+
+Besides that, doing the following is generally enough:
+
+## For OTP installations
+
+```sh
+# Download the new release
+su pleroma -s $SHELL -lc "./bin/pleroma_ctl update"
+
+# Migrate the database, you are advised to stop the instance before doing that
+su pleroma -s $SHELL -lc "./bin/pleroma_ctl migrate"
+```
+
+## For from source installations (using git)
+
1. Go to the working directory of Pleroma (default is `/opt/pleroma`)
2. Run `git pull`. This pulls the latest changes from upstream.
3. Run `mix deps.get`. This pulls in any new dependencies.