2019-03-28 16:46:30 +00:00
# Updating your instance
2020-01-15 08:12:24 +00:00
2020-07-09 03:15:51 +00:00
You should **always check the [release notes/changelog](https://git.pleroma.social/pleroma/pleroma/-/releases)** in case there are config deprecations, special update steps, etc.
2020-01-15 08:12:24 +00:00
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)
2019-04-01 13:23:32 +00:00
1. Go to the working directory of Pleroma (default is `/opt/pleroma` )
2022-05-12 16:02:58 +00:00
2. Run `git pull` [^1]. This pulls the latest changes from upstream.
2020-08-28 13:50:21 +00:00
3. Run `mix deps.get` [^1]. This pulls in any new dependencies.
2019-04-01 13:23:32 +00:00
4. Stop the Pleroma service.
2020-08-28 13:50:21 +00:00
5. Run `mix ecto.migrate` [^1] [^2]. This task performs database migrations, if there were any.
2019-04-01 13:26:46 +00:00
6. Start the Pleroma service.
2019-03-28 16:46:30 +00:00
2022-05-12 16:02:58 +00:00
[^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.
2020-08-28 13:50:21 +00:00
[^2]: Prefix with `MIX_ENV=prod` to run it using the production config file.