pleroma/docs/administration/updating.md

# 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

```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)

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.migrate`[^1]. 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.
Move out of Gitlab Wiki I understand that this change is quite unreadable and hard to review, sorry for forgetting to do atomic commits. This patch does not change too much content wise, it just * Gets everything from gitlab wiki * Removes some specific gitlab hacks * Formats all documentation file names to be in snake case so they look the same way as our code does 2019-03-28 12:46:30 -04:00			`# Updating your instance`
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 03:12:24 -05:00
			`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`

			```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)`

Instruct to stop the service only after git pulling and getting deps to minimize downtimes 2019-04-01 09:23:32 -04: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.`
Move out of Gitlab Wiki I understand that this change is quite unreadable and hard to review, sorry for forgetting to do atomic commits. This patch does not change too much content wise, it just * Gets everything from gitlab wiki * Removes some specific gitlab hacks * Formats all documentation file names to be in snake case so they look the same way as our code does 2019-03-28 12:46:30 -04:00			5. Run `mix ecto.migrate`[^1]. This task performs database migrations, if there were any.
restart makes no sense here as we instructed to stop the service before 2019-04-01 09:26:46 -04:00			`6. Start the Pleroma service.`
Move out of Gitlab Wiki I understand that this change is quite unreadable and hard to review, sorry for forgetting to do atomic commits. This patch does not change too much content wise, it just * Gets everything from gitlab wiki * Removes some specific gitlab hacks * Formats all documentation file names to be in snake case so they look the same way as our code does 2019-03-28 12:46:30 -04:00
			[^1]: Prefix with `MIX_ENV=prod` to run it using the production config file.