From 6e1e9f0c1abc3cbbf057cd973d5775233551c89a Mon Sep 17 00:00:00 2001
From: M33 <327-m33@git.qoto.org>
Date: Mon, 27 Dec 2021 18:40:01 +0000
Subject: [PATCH] Update README.md

---
 README.md | 21 ++++++++++++++++++++-
 1 file changed, 20 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 2764439..5b4d142 100644
--- a/README.md
+++ b/README.md
@@ -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)
-- 
GitLab