mirror_maker/misskey-admin-scripts-n-tips
1
0
Fork 1
mirror of https://git.qoto.org/m33/misskey-admin-scripts-n-tips.git synced 2024-10-22 23:19:08 +00:00
Code Issues Projects Releases Packages Wiki Activity

Merge branch 'master' of https://git.qoto.org/m33/misskey-admin-scripts-n-tips

Browse source
This commit is contained in:
m33 2021-12-27 18:44:12 +00:00
commit 124bc52ef9
1 changed files with 20 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

21
README.md
View file

@ -20,4 +20,23 @@ Get container ID from name (used in other scripts)
## 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.
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)