2019-03-28 10:46:30 -06:00
# Updating your instance
2020-01-15 01:12:24 -07:00
2022-07-03 09:18:43 -06:00
You should **always check the [release notes/changelog](https://akkoma.dev/AkkomaGang/akkoma/src/branch/develop/CHANGELOG.md)** 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
2022-07-03 09:18:43 -06:00
su akkoma -s $SHELL -lc "./bin/pleroma_ctl update"
2020-01-15 01:12:24 -07:00
# Migrate the database, you are advised to stop the instance before doing that
2022-07-03 09:18:43 -06:00
su akkoma -s $SHELL -lc "./bin/pleroma_ctl migrate"
2020-01-15 01:12:24 -07:00
```
## For from source installations (using git)
2022-07-03 09:18:43 -06:00
1. Go to the working directory of Akkoma (default is `/opt/akkoma` )
2022-05-12 10:02:58 -06:00
2. Run `git pull` [^1]. This pulls the latest changes from upstream.
2020-08-28 07:50:21 -06:00
3. Run `mix deps.get` [^1]. This pulls in any new dependencies.
2022-07-03 09:18:43 -06:00
4. Stop the Akkoma service.
2020-08-28 07:50:21 -06:00
5. Run `mix ecto.migrate` [^1] [^2]. This task performs database migrations, if there were any.
2022-07-03 09:18:43 -06:00
6. Start the Akkoma service.
2019-03-28 10:46:30 -06:00
2022-07-03 09:18:43 -06:00
[^1]: Depending on which install guide you followed (for example on Debian/Ubuntu), you want to run `git` and `mix` tasks as `akkoma` user by adding `sudo -Hu akkoma` before the command.
2020-08-28 07:50:21 -06:00
[^2]: Prefix with `MIX_ENV=prod` to run it using the production config file.