Switch novelly-data to a bind mount at /mnt/storage/app/novelly/data
CI / build-and-push (push) Successful in 41s
CI / deploy (push) Successful in 8s

Named docker volume replaced with an explicit host path per user request.
Requires the path to exist on the QA server and any data from the old
novelly-data volume to be copied over manually before the next deploy.
This commit is contained in:
James Wampler
2026-08-19 14:46:35 -07:00
parent 8f93dce065
commit 304b8b4c59
+5 -8
View File
@@ -1,8 +1,9 @@
name: novelly
# Persistent LAN deployment, pulled and recreated by CI on every push to main.
# Unlike a throwaway QA stack, this one keeps its data volume across deploys — `down`
# is run without `-v` so the author's novel data survives a redeploy.
# Unlike a throwaway QA stack, this one keeps its data across deploys — `down` is run
# without `-v` and /data is a bind mount to /mnt/storage/app/novelly/data on the host,
# not a docker-managed volume, so the author's novel data survives a redeploy.
services:
api:
@@ -13,7 +14,7 @@ services:
Cors__Origins__0: "http://localhost:${WEB_PORT:-6173}"
ANTHROPIC_API_KEY: ${ANTHROPIC_API_KEY:-}
volumes:
- novelly-data:/data
- /mnt/storage/app/novelly/data:/data
networks:
- novelly
healthcheck:
@@ -43,7 +44,7 @@ services:
environment:
ConnectionStrings__Novel: "Data Source=/data/novel.db"
volumes:
- novelly-data:/data
- /mnt/storage/app/novelly/data:/data
networks:
- novelly
profiles: ["tools"]
@@ -51,7 +52,3 @@ services:
networks:
novelly:
name: novelly-net
volumes:
novelly-data:
name: novelly-data