docs: note the docker-compose.yml rsync footgun in the NUC deploy process
Some checks failed
Test and SonarQube / quality (push) Has been cancelled

Rsyncing the tree without excluding docker-compose.yml overwrites the
NUC's own compose file with the DGX's (wrong build/image, dgx_net/
docker-socket-proxy the NUC doesn't have), breaking `docker compose up -d`.
Hit and fixed during the v1.54.0 deploy.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
mARTin-B78 2026-09-27 15:12:24 +02:00
parent 3c91156e5c
commit d94d85b21b

View File

@ -201,6 +201,11 @@ English magazine text before it is marked complete.
`docker-compose.yml`, since that host has no `.git` checkout of its own to diff against, only the rsynced tree. `docker-compose.yml`, since that host has no `.git` checkout of its own to diff against, only the rsynced tree.
A code change means: re-rsync the tree (excluding `.git`, `config/`, `logs/`), `docker compose build`, `docker A code change means: re-rsync the tree (excluding `.git`, `config/`, `logs/`), `docker compose build`, `docker
compose up -d` — no separate push/pull step, same as the DGX's own bind-mount-and-recreate pattern. compose up -d` — no separate push/pull step, same as the DGX's own bind-mount-and-recreate pattern.
**Footgun confirmed 2026-09-27:** `docker-compose.yml` must ALSO be excluded from the rsync (`--exclude
docker-compose.yml`) — otherwise it silently overwrites the NUC's own compose file with the DGX's (wrong
`build`/`image`, `dgx_net`/`docker-socket-proxy` the NUC doesn't have), and `docker compose up -d` then fails with
`network dgx_net declared as external, but could not be found`. Recovery: `cp docker-compose.nuc.yml
docker-compose.yml` on the NUC, then `up -d --force-recreate`.
## Deferred — public multi-user readiness (cross-app initiative) ## Deferred — public multi-user readiness (cross-app initiative)