1.9 KiB
1.9 KiB
Remote Deploy Debug Log
Date: 2026-05-03
Target: daniel@172.30.16.10:/opt/KonCad
Summary
- The remote host was already running
koncad-koncad-1on port8080. /opt/KonCadonly contained deployment metadata (Dockerfile,docker-compose.yml, workflow files) and did not containapp/.- The original deploy flow synced source files to
/opt/KonCad, butdocker-compose.ymlused only the published image, so remote source changes were not applied unless the host rebuilt separately.
Changes made
- Added
build: .todocker-compose.ymlso the server can build from the synced checkout. - Updated
deploy.shto rundocker compose up -d --buildon the remote host afterrsync. - Added
--no-remote-restartfor cases where only file sync is wanted. - Added
.dockerignoreand tightenedrsyncexcludes so editor metadata and docs are not part of the deployment payload.
Remote checks performed
- Confirmed container status with
docker ps. - Confirmed the live app answered on
http://127.0.0.1:8080/. - Confirmed the container mounts
/opt/caddyread-only and persists/datain thekoncad_koncad_datavolume. - Confirmed existing auth state is already present in
/data/.auth. - Rebuilt the container on the host with
docker compose up -d --build. - Verified
/opt/KonCad/app/index.phpand/var/www/html/index.phphave the same SHA-256 hash after deploy. - Verified
php -l /var/www/html/index.phppasses inside the running container. - Verified KonCad can reach
http://caddy:2019/config/from inside the container. - Cleaned stale
.claude,.superpowers, anddocsdirectories from/opt/KonCadon the server.
Notes
- Local PHP tooling was not available in this workspace (
php: command not found), so syntax/runtime verification was done on the remote host. - The Apache log still shows the harmless
Could not reliably determine the server's fully qualified domain namestartup warning from the base image.