Difference between revisions of "ITSquad/Mastodon/Maintenance"
m (→How to upgrade?) |
(→How to upgrade?: simplify upgrade process) |
||
| Line 11: | Line 11: | ||
# git checkout vX.X.X # jump to the version where we want to update | # git checkout vX.X.X # jump to the version where we want to update | ||
# git stash pop # restore your changes | # git stash pop # restore your changes | ||
| − | |||
# docker-compose pull # pull from the docker-hub https://hub.docker.com/r/gargron/mastodon/ | # docker-compose pull # pull from the docker-hub https://hub.docker.com/r/gargron/mastodon/ | ||
# docker-compose stop # stop the containers | # docker-compose stop # stop the containers | ||
| − | # docker start | + | # docker-compose start db # start the db container |
| − | # docker exec - | + | # docker-compose exec db pg_dump -U postgres -Fc postgres > ../dump_$(date +%d-%m-%Y"_"%H_%M_%S).sql # backup the database |
# tail ../your_dump_file.sql # check if the backup worked, with your_dump_file.sql being the dumpfile you have created in the previous step. | # tail ../your_dump_file.sql # check if the backup worked, with your_dump_file.sql being the dumpfile you have created in the previous step. | ||
# docker-compose down # shut down the containers. | # docker-compose down # shut down the containers. | ||
| Line 29: | Line 28: | ||
Don't panic. You can restore the database backup as follows: | Don't panic. You can restore the database backup as follows: | ||
# docker-compose stop | # docker-compose stop | ||
| − | # docker | + | # docker-compose start db |
| − | # docker exec | + | # docker-compose exec db dropdb postgres -U postgres # remove the db !!!!!!! |
| − | # docker exec | + | # docker-compose exec db createdb postgres -U postgres # create a fresh and new db |
# cat ../your_dump_file.sql | docker exec -i mastodon_db_1 psql -U postgres # restore the database, with "your_dump_file" being a database backup | # cat ../your_dump_file.sql | docker exec -i mastodon_db_1 psql -U postgres # restore the database, with "your_dump_file" being a database backup | ||
# docker-compose down | # docker-compose down | ||
| Line 38: | Line 37: | ||
You can also go to a previous version of Mastodon with: | You can also go to a previous version of Mastodon with: | ||
# git checkout vX.X.X | # git checkout vX.X.X | ||
| − | # sed s/ | + | # sed s/:latest/:vX.X.X/g docker-compose.yml # don't forget to change this back to "latest" when things get fixed |
# docker-compose pull | # docker-compose pull | ||
Revision as of 12:13, 23 March 2018
This page aims to describe procedures to maintain the Pirate Party's Mastodon instance.
How to upgrade?
A script called update.sh located in /home/mastodon will reproduce the steps below. Note: this script stops at step 14 and does not go further.
Before running this script or the following commands, please check the instruction for the current release. Sometimes, aditionnal actions are needed (other than migrate database and compile assets)
- git fetch # update the git branch
- git stash # prevent changes made to the files to be overwritten (mainly, the docker-compose.yml file)
- git checkout vX.X.X # jump to the version where we want to update
- git stash pop # restore your changes
- docker-compose pull # pull from the docker-hub https://hub.docker.com/r/gargron/mastodon/
- docker-compose stop # stop the containers
- docker-compose start db # start the db container
- docker-compose exec db pg_dump -U postgres -Fc postgres > ../dump_$(date +%d-%m-%Y"_"%H_%M_%S).sql # backup the database
- tail ../your_dump_file.sql # check if the backup worked, with your_dump_file.sql being the dumpfile you have created in the previous step.
- docker-compose down # shut down the containers.
- You'll maybe get "ERROR: An HTTP request took too long to complete" and other errors. Don't mind this and just wait 'till it's done.
- docker-compose run --rm web rails db:migrate # upgrade the database
- docker-compose run --rm web rails assets:precompile # complie the assets
- docker-compose up -d # start the mastodon instance (create new volumes)
- docker-compose logs -ft web # (optional) if you want to monitor the progress. Once this is done you ctrl+c
- docker volume prune # remove all unused volumes
What to do when something went wrong?
Don't panic. You can restore the database backup as follows:
- docker-compose stop
- docker-compose start db
- docker-compose exec db dropdb postgres -U postgres # remove the db !!!!!!!
- docker-compose exec db createdb postgres -U postgres # create a fresh and new db
- cat ../your_dump_file.sql | docker exec -i mastodon_db_1 psql -U postgres # restore the database, with "your_dump_file" being a database backup
- docker-compose down
- docker-compose up -d
You can also go to a previous version of Mastodon with:
- git checkout vX.X.X
- sed s/:latest/:vX.X.X/g docker-compose.yml # don't forget to change this back to "latest" when things get fixed
- docker-compose pull
How to backup?
Backups of the database are not enough. We need to backup images, user feeds, etc.
We can simply copy the whole Mastodon's directory. For instance:
tar cvf /home/mastodon/backup/mastodon.tar /home/mastodon/mastodon/
Then, we backup the database:
docker exec -t mastodon_db_1 pg_dumpall -c -U postgres > /home/mastodon/backup/db/dump_`date +%d-%m-%Y"_"%H_%M_%S`.sql
It can be interesting to execute the following command before doing a backup:
docker-compose run --rm web rails mastodon:media:remove_remote
This will remove local cache of media older than NUM_DAYS (=7 by default, but we can change this value). Note that this command is executed every day.
Currently, we do not provide automatic backups!
