m3

UNRAID.md

@@ -37,6 +37,8 @@ docker run -d \
   -p 8080:3000 \
   -e PORT=3000 \
   -e LOG_LEVEL=info \
+  -e DATABASE_PATH=/data/stellar.sqlite \
+  -v /mnt/user/appdata/stellar:/data \
   stellar:local
 ```
 
@@ -69,6 +71,8 @@ docker run -d \
   -p 8080:3000 \
   -e PORT=3000 \
   -e LOG_LEVEL=info \
+  -e DATABASE_PATH=/data/stellar.sqlite \
+  -v /mnt/user/appdata/stellar:/data \
   <your-registry>/stellar:<tag>
 ```
 
@@ -107,6 +111,8 @@ docker run -d \
   -p 8080:3000 \
   -e PORT=3000 \
   -e LOG_LEVEL=info \
+  -e DATABASE_PATH=/data/stellar.sqlite \
+  -v /mnt/user/appdata/stellar:/data \
   stellar:local
 ```
 
@@ -120,7 +126,7 @@ docker compose up -d --build
 
 ## Notes
 
-- There is no persistent SQLite mount yet because M3 persistence has not been implemented.
-- When SQLite is added, bind-mount a host path such as `/mnt/user/appdata/stellar/data` into the container.
+- SQLite persistence now defaults to `/data/stellar.sqlite` in containers.
+- The examples above bind `/mnt/user/appdata/stellar` into `/data` so profile data survives container recreation.
 - If Unraid already uses port `8080`, change the host-side port mapping and browse to that port instead.
 - Logs are written to container stdout/stderr and can be viewed from the Unraid Docker UI or with `docker logs stellar`.