webmail-client

T

lukasandClaude Opus 5 8ddac220b8 Deploy: flatten the prod stack into one root compose file

Synology Container Manager rejects the compose file with "Property include is
not allowed": DSM bundles an older Compose than the one that introduced
`include:` (v2.20). The root docker-compose.yml existed purely so the NAS GUIs
would find production rather than the dev service stack, so using a feature
the GUI cannot parse defeated its only purpose.

docker/docker-compose.prod.yml is now the root docker-compose.yml itself — one
plain, flat file, no indirection. Build contexts go from `..` to `.`, the
backup sidecar mounts ./docker/backup.sh, and webmail.sh points at the new
path. Nothing else changed: same services, same project name webmail-prod,
same guards.

The header now says why the file lives at the root and to keep it free of
newer compose features, so this does not get "tidied up" back into something
DSM refuses.

Verified with `docker compose up -d --wait` from the repo root as the GUI
invokes it: all services healthy, account created, backup sidecar resolving
its script at the new path, and webmail.sh status/doctor/down driving the same
stack.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Nux3LCu4zP9nih4BRhPyHw

2026-09-14 19:37:23 +02:00

backend

Deploy: production Docker stack for a single host (Synology/QNAP NAS)

2026-09-14 18:53:50 +02:00

deploy

Deploy: explain the root-owned env file instead of leaking "Permission denied"

2026-09-14 19:29:22 +02:00

docker

Deploy: flatten the prod stack into one root compose file

2026-09-14 19:37:23 +02:00

docs

Deploy: explain the root-owned env file instead of leaking "Permission denied"