The NFS blocker from TODO.md's deployment entry is resolved (export
set up by the user on the DGX); picks up from there and completes the
deployment end to end.
- Mounted the DGX's TTS_Voices export read-write on the NUC at
/mnt/dgx-tts-voices, persisted in /etc/fstab -- confirmed writable
and confirmed the NUC instance sees the DGX's real voice library
(344 voices), not a separate copy.
- Deployed by rsyncing the working tree from the DGX (excluding .git,
config/, logs/ and other local-only paths) and building the image
directly on the NUC, rather than pulling ghcr.io/martin-b78/... --
that registry copy turned out to be both several versions stale and
private with no credentials configured on the NUC, and the source
was already right there to build from.
- Found and fixed a real gap while wiring it up: vision_ocr_url and
vision_ocr_fallback_url default to host.docker.internal, which
resolves to whichever host the container is running on -- correct
on the DGX itself, silently wrong on the NUC (would have pointed at
the NUC's own nonexistent OCR engine). Pinned both explicitly to the
DGX's LAN IP via environment overrides.
- The container crash-looped on first start (sqlite3.OperationalError:
unable to open database file) because docker compose had created
config/ and logs/ root-owned under this session's root SSH access to
the NUC, while the image's app user is uid 1000 -- chown -R 1000:1000
fixed it.
- New docker-compose.nuc.yml, tracked here as the reviewable reference
for that host (docker-compose.yml stays the DGX's own -- different
build/network/socket-proxy shape). Deployed to the NUC as its own
docker-compose.yml, since that host has no .git checkout to diff
against, only the rsynced tree.
Verified: container stable (no restart loop), HTTP 200, settings
confirm all four engine URLs correctly resolve to the DGX, voice count
matches the DGX exactly, restart policy is unless-stopped.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
