sjw/pleroma
1
0
Fork 0
mirror of https://git.pleroma.social/sjw/pleroma.git synced 2024-11-16 22:46:47 +01:00
Code Issues Releases Wiki Activity
8eebc75c15
pleroma/docs/administration/updating.md
ilja e02eb8de3e Add OTP to updating.md 
* I removed the Update section from the OTP install and added it to updating.md
* I also added a link to the updating.md from the OTP install page
* I added a Questions section to the OTP install, similar to the debian_based_en.md
* Restructured the updating.md a bit

I would very much also like to link to the changelog, but I don't know how to do it because I can't find the page in the docs?
2020-01-15 09:12:24 +01:00

935 B
Raw Blame History

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

# 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.
  4. Stop the Pleroma service.
  5. Run mix ecto.migrate1. 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. ↩︎