From fe707d5f24f79abf6ffbc282613cec2ea754ad22 Mon Sep 17 00:00:00 2001 From: disqualifier Date: Wed, 1 Jul 2026 02:14:50 -0400 Subject: [PATCH] deploy: clarify container path = where your code reads/writes Make the volume mapping explicit: the right-hand mount path is where the app writes. WORKDIR is /app, so code writing to ./cache lands in /app/cache (this mount); same for /app/logs and /app/config. Removes ambiguity about which side of the volume line the code targets. Verified: mkdocs build --strict clean. Signed-off-by: disqualifier --- docs/deploy.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/deploy.md b/docs/deploy.md index da9201a..ffe0699 100644 --- a/docs/deploy.md +++ b/docs/deploy.md @@ -155,8 +155,12 @@ volumes: The deploy layer injects `MOUNTS_DIR` and auto-creates the dir — but you **uncomment** the line and pick the container path (`/app/data` here), since that's app-specific and can't be auto-mounted. -7. Named volume with a **bare name** — ephemeral, auto-namespaced per service at - deploy time so it can't collide. +7. Named volume mounted at **`/app/cache`** — ephemeral scratch. The **right-hand + path is where your code writes**: `WORKDIR` is `/app`, so if your app writes to + `./cache` (or `/app/cache`), that's this mount. Same rule for logs (`/app/logs`) + and config (`/app/config`) — match the container path to where your code reads + and writes. The volume name is a bare name, auto-namespaced per service at deploy + so it can't collide. 8. Declare bare (`cache`, not `myapp_cache`). Deploy auto-prefixes it. !!! tip "Three tiers of storage"