aboutsummaryrefslogtreecommitdiff
path: root/docs/administration/updating.md
diff options
context:
space:
mode:
authorMaksim Pechnikov <parallel588@gmail.com>2020-02-25 07:15:33 +0300
committerMaksim Pechnikov <parallel588@gmail.com>2020-02-25 07:22:56 +0300
commit10f452ad1feae9a882b6dc4cd35e09adb7e78208 (patch)
tree62083f08fbe99cd38002d1f6896cd2fd79675320 /docs/administration/updating.md
parent28701c08ad9219219a32f31b2ed9dcb83f92cd59 (diff)
parent035c2c1415ed46abb268cf85c141384416a799e2 (diff)
downloadpleroma-10f452ad1feae9a882b6dc4cd35e09adb7e78208.tar.gz
Merge branch 'develop' into issue/1276
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.