logo

pleroma

My custom branche(s) on git.pleroma.social/pleroma/pleroma git clone https://hacktivis.me/git/pleroma.git
commit: 7466136ad3288cc2b442495d40af6e0787b250fb
parent bdca5f5d68022ba8cee257c3602703fa09bd4c6b
Author: Haelwenn <contact+git.pleroma.social@hacktivis.me>
Date:   Sun, 22 May 2022 17:09:54 +0000

Merge branch 'lewdthewides-develop-patch-48691' into 'develop'

Instruct users to run 'git pull' as the pleroma user

See merge request pleroma/pleroma!3667

Diffstat:

Mdocs/administration/updating.md4++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/administration/updating.md b/docs/administration/updating.md @@ -17,11 +17,11 @@ 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. +2. Run `git pull` [^1]. This pulls the latest changes from upstream. 3. Run `mix deps.get` [^1]. This pulls in any new dependencies. 4. Stop the Pleroma service. 5. Run `mix ecto.migrate` [^1] [^2]. This task performs database migrations, if there were any. 6. Start the Pleroma service. -[^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. +[^1]: Depending on which install guide you followed (for example on Debian/Ubuntu), you want to run `git` and `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.