diff options
author | lain <lain@soykaf.club> | 2020-02-20 12:03:21 +0000 |
---|---|---|
committer | lain <lain@soykaf.club> | 2020-02-20 12:03:21 +0000 |
commit | d536a00d42e2d6747961755fd28f3dd1f646148e (patch) | |
tree | 710d5e020483f3a2681e4eb1be5b6b5f2326a268 /docs/administration | |
parent | e0b2de63853e9a14b72faddf6e1180a098728205 (diff) | |
parent | e02eb8de3ec8130e9808c6a54a5c78f7ec8feb23 (diff) | |
download | pleroma-d536a00d42e2d6747961755fd28f3dd1f646148e.tar.gz pleroma-d536a00d42e2d6747961755fd28f3dd1f646148e.zip |
Merge branch 'docs_updating' into 'develop'
DOCS Add OTP to updating.md
See merge request pleroma/pleroma!2108
Diffstat (limited to 'docs/administration')
-rw-r--r-- | docs/administration/updating.md | 17 |
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. |