Mirror for Misske scripts and stuff
Find a file
2021-12-27 18:44:12 +00:00
backup_postgres.sh load scripts 2021-12-27 18:16:28 +00:00
cleanup_docker.sh load scripts 2021-12-27 18:16:28 +00:00
get_container_id.sh load scripts 2021-12-27 18:16:28 +00:00
misskey-arm64.yml upload docker-compose for arm64 2021-12-27 18:43:46 +00:00
README.md Update README.md 2021-12-27 18:40:01 +00:00

misskey-admin-scripts-n-tips

A collection of scripts and tips to make a Misskey admin's life a little bit easyer

Abstract: a VPS, Docker, a Misskey instance, what could save you some time ?

Scripts list:

backup_postgres.sh

A daily backup for your docker postgresql database, run it daily It will cycle with the day of week (1..7)

cleanup_docker.sh

Prune all orphaned images, and stopped containers

get_container_id.sh

Get container ID from name (used in other scripts)

Tips list:

Separate code and data

The default misskey docker install guide will place misskey code and your instance data in the same directory. Is something goes wrong on a later time, you may accidentally trash your datas (docker volumes mounted for the postgres database, redis cache...).

Separate the misskey code (git clone...) from you container's volumes, something like this should do:

/usr/local/misskey/code
/usr/local/misskey/data

You will need a custom yaml file for docker-compose, but it's worth it (see sample yaml file).

Manage your misskey instance containers with docker-compose and the right path for code and datas:

docker-compose --project-directory=/usr/local/misskey/data -f /usr/local/misskey/data/<your custom docker-compose>.yml 

Ressources list:

misskey-arm64.yml:

A docker-compose yaml file, for an arm64 (raspberry pi, VPS arm instances)