Files
KonCad/docs/deployments/2026-05-03-remote-deploy-debug.md
Daniel e9035bf6fe
Publish Docker image / build (push) Failing after 6s
Improve Caddyfile editor for demo-style configs
2026-05-03 18:59:32 +02:00

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-1 on port 8080.
  • /opt/KonCad only contained deployment metadata (Dockerfile, docker-compose.yml, workflow files) and did not contain app/.
  • The original deploy flow synced source files to /opt/KonCad, but docker-compose.yml used only the published image, so remote source changes were not applied unless the host rebuilt separately.

Changes made

  • Added build: . to docker-compose.yml so the server can build from the synced checkout.
  • Updated deploy.sh to run docker compose up -d --build on the remote host after rsync.
  • Added --no-remote-restart for cases where only file sync is wanted.
  • Added .dockerignore and tightened rsync excludes 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/caddy read-only and persists /data in the koncad_koncad_data volume.
  • 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.php and /var/www/html/index.php have the same SHA-256 hash after deploy.
  • Verified php -l /var/www/html/index.php passes inside the running container.
  • Verified KonCad can reach http://caddy:2019/config/ from inside the container.
  • Cleaned stale .claude, .superpowers, and docs directories from /opt/KonCad on 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 name startup warning from the base image.