summaryrefslogtreecommitdiff
path: root/docs/administration/updating.md
diff options
context:
space:
mode:
authorIvan Tashkinov <ivantashkinov@gmail.com>2020-02-22 09:31:43 +0300
committerIvan Tashkinov <ivantashkinov@gmail.com>2020-02-22 09:31:43 +0300
commit8f0ca19b9cafeedc70df2d60bd7bd7c6bf7aa160 (patch)
treef14a1ef01c90124b33b2866117ed2995e32ab369 /docs/administration/updating.md
parent0d14c3f41053f97d23fa9295745a817c08010969 (diff)
parent114e7b764ed5ae03211cca40e7b19f33292b3d1c (diff)
downloadpleroma-8f0ca19b9cafeedc70df2d60bd7bd7c6bf7aa160.tar.gz
pleroma-8f0ca19b9cafeedc70df2d60bd7bd7c6bf7aa160.zip
Merge remote-tracking branch 'remotes/origin/develop' into 1505-threads-federation
# Conflicts: # CHANGELOG.md # config/config.exs
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.