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)¶
- Go to the working directory of Pleroma (default is
git pull. This pulls the latest changes from upstream.
mix deps.get. This pulls in any new dependencies.
- Stop the Pleroma service.
mix ecto.migrate[^1]. This task performs database migrations, if there were any.
- Start the Pleroma service.
[^1]: Prefix with
MIX_ENV=prod to run it using the production config file.