mirrors/pleroma
1
0
Fork 0
mirror of https://git.pleroma.social/pleroma/pleroma.git synced 2025-01-10 09:15:25 +00:00
Code Issues Projects Releases Wiki Activity
pleroma/docs/admin/updating.md

10 lines
445 B
Markdown
Raw Normal View History

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 16:46:30 +00:00
# Updating your instance
Instruct to stop the service only after git pulling and getting deps to minimize downtimes
2019-04-01 13:23:32 +00: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 16:46:30 +00: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 13:26:46 +00: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 16:46:30 +00:00
[^1]: Prefix with `MIX_ENV=prod` to run it using the production config file.
Reference in a new issue Copy permalink