mirror of
https://git.qoto.org/m33/misskey-admin-scripts-n-tips.git
synced 2024-10-22 23:19:08 +00:00
42 lines
1.4 KiB
Markdown
42 lines
1.4 KiB
Markdown
# 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)
|