misskey-admin-scripts-n-tips/README.md

47 lines
1.6 KiB
Markdown
Raw Normal View History

2021-12-27 17:59:36 +00:00
# misskey-admin-scripts-n-tips
2021-12-27 18:23:21 +00:00
A collection of scripts and tips to make a Misskey admin's life a little bit easyer
2021-12-27 18:20:49 +00:00
2021-12-27 18:26:55 +00:00
Abstract: a VPS, Docker, a Misskey instance, what could save you some time ?
# Scripts list:
2021-12-27 18:20:49 +00:00
## 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)
2021-12-27 18:26:55 +00:00
# Tips list:
## Separate code and data
2021-12-27 18:40:01 +00:00
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)
2021-12-27 19:01:52 +00:00
## Yolk__bad-blood__custom-emojis.zip:
Yolk emojis, from [Bad-blood on Devianart](https://www.deviantart.com/bad-blood/art/Y-o-l-k-s-78118255). This zip file is ready to be imported on misskey (files with names and tags)