From d94d85b21bc4da749094c86e0f08145f57bc347a Mon Sep 17 00:00:00 2001 From: mARTin-B78 Date: Sun, 27 Sep 2026 15:12:24 +0200 Subject: [PATCH] docs: note the docker-compose.yml rsync footgun in the NUC deploy process 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 --- TODO.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/TODO.md b/TODO.md index 0b2cf7e..07353b8 100644 --- a/TODO.md +++ b/TODO.md @@ -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. 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. + **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)