squeegily
/
pleroma
1
0
Fork 0
Code Issues 0 Pull Requests 0 Releases 42 Wiki Activity
Fork of Pleroma with site-specific changes and feature branches https://git.pleroma.social/pleroma/pleroma
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
7259 Commits
154 Branches
503MB
Tree: 5cb03fe801
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '5cb03fe801'
${ noResults }
pleroma/docs/administration/updating.md

updating.md 445B
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
5 years ago
Instruct to stop the service only after git pulling and getting deps to minimize downtimes
5 years ago
​
​
​
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
5 years ago
restart makes no sense here as we instructed to stop the service before
5 years ago
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
5 years ago
​
 123456789 
  1. # Updating your instance

  2. 1. Go to the working directory of Pleroma (default is `/opt/pleroma`)

  3. 2. Run `git pull`. This pulls the latest changes from upstream.

  4. 3. Run `mix deps.get`. This pulls in any new dependencies.

  5. 4. Stop the Pleroma service.

  6. 5. Run `mix ecto.migrate`[^1]. This task performs database migrations, if there were any.

  7. 6. Start the Pleroma service.

  8. 

  9. [^1]: Prefix with `MIX_ENV=prod` to run it using the production config file.