2019-03-28 10:46:30 -06:00
# Updating your instance
2020-01-15 01:12:24 -07:00
2020-07-08 21:15:51 -06: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 01:12:24 -07: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 07:23:32 -06:00
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.
2019-03-28 10:46:30 -06:00
5. Run `mix ecto.migrate` [^1]. This task performs database migrations, if there were any.
2019-04-01 07:26:46 -06:00
6. Start the Pleroma service.
2019-03-28 10:46:30 -06:00
[^1]: Prefix with `MIX_ENV=prod` to run it using the production config file.