Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
O
operations
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
social.coop
tech
operations
Commits
5067656c
Commit
5067656c
authored
2 years ago
by
David Mynors
Browse files
Options
Downloads
Patches
Plain Diff
Add mastodon upgrade notes
parent
8609baa7
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+29
-0
29 additions, 0 deletions
README.md
with
29 additions
and
0 deletions
README.md
+
29
−
0
View file @
5067656c
...
...
@@ -119,3 +119,32 @@ deployment/wiki/webhook_secret
```
On the server it lives at:
`/opt/social.coop/wiki.social.coop/`
and is running as the systemd service
`wiki.social.coop.service`
.
## Mastodon upgrade notes
-
get current version from social.coop
-
find next version from mastodon github releases
-
check upgrade notes
-
we are on docker!
-
check whether there are DB migrations
-
make backup?
`systemctl start pg-dump-to-s3.service`
-
takes 15 mins or so?
-
separate command to see backup progress
-
make merge request on git.coop sauce repo to bump version in a couple of
places in docker-compose.yaml
-
`git diff v3.1.2..v3.1.3 -- docker-compose.yml`
in mastodon repo after pulling
to check whether there were any changes we should consider mirroring to our
docker-compose file
-
could be cool to make these merge requests in advance
-
write a toot announcing upgrade and boost on admin account
-
touch file on server to activate maintenance mode
-
actually do the upgrade
-
migration command creates a fresh web container and runs the migration
command and then deletes that new container
-
turn maintenance mode off
-
we copy static assets outside of the container so they can be served by nginx
-
there's a command for this which moves stuff into a temporary dir in nginx
and pulls assets out of docker container into that folder in docker
container
-
ssh forwarding is nice, then with
`sudo -E -s`
you have ssh access to stuff
you do from host machine(?)
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment