diff options
| author | Shpuld Shpludson <shp@cock.li> | 2020-08-28 13:50:21 +0000 |
|---|---|---|
| committer | Shpuld Shpludson <shp@cock.li> | 2020-08-28 13:50:21 +0000 |
| commit | 35da3be9ddf2df042153978308178c94afe25737 (patch) | |
| tree | f5f26b3daf405a4485d738e3b61cc2b302df3c6f | |
| parent | 6b01a09a08e14c415ac3bd48ea28c742ee7a3dc8 (diff) | |
Add mention of sudo -Hu pleroma to docs
| -rw-r--r-- | docs/administration/updating.md | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/administration/updating.md b/docs/administration/updating.md index c994f3f16..ef2c9218c 100644 --- a/docs/administration/updating.md +++ b/docs/administration/updating.md @@ -18,9 +18,10 @@ su pleroma -s $SHELL -lc "./bin/pleroma_ctl migrate" 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. +3. Run `mix deps.get` [^1]. This pulls in any new dependencies. 4. Stop the Pleroma service. -5. Run `mix ecto.migrate`[^1]. This task performs database migrations, if there were any. +5. Run `mix ecto.migrate` [^1] [^2]. This task performs database migrations, if there were any. 6. Start the Pleroma service. -[^1]: Prefix with `MIX_ENV=prod` to run it using the production config file. +[^1]: Depending on which install guide you followed (for example on Debian/Ubuntu), you want to run `mix` tasks as `pleroma` user by adding `sudo -Hu pleroma` before the command. +[^2]: Prefix with `MIX_ENV=prod` to run it using the production config file. |