mirror of
https://git.qoto.org/m33/misskey-admin-scripts-n-tips.git
synced 2024-10-22 15:09:06 +00:00
Update README.md
This commit is contained in:
parent
1bb06bdb0f
commit
6e1e9f0c1a
1 changed files with 20 additions and 1 deletions
21
README.md
21
README.md
|
@ -20,4 +20,23 @@ Get container ID from name (used in other scripts)
|
||||||
|
|
||||||
## Separate code and data
|
## 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)
|
||||||
|
|
Loading…
Reference in a new issue