daybook/deploy
peter ca8e364010 Fix healthcheck + verify commands; reframe deploy runbook for a capable agent
Real bug: the container healthcheck (and the docs' verify step) hit
/api/capabilities, which returns 403 unauthenticated; curl --fail treats
403 as an error, so a healthy container would report "unhealthy" and the
verify step would look like a failure. Healthcheck now hits /accounts/login/
(200, no auth). Verify commands now print the status code and note not to
use curl -f on the 403.

Also reframed cloud_agent_deploy.md's intro for an Opus-class deploy agent:
it's a guide + Daybook-specific gotchas, not a rigid script — points at the
authoritative sources (repo incl. the git-SSH :2222 note, deploy/ files,
requirements.txt deps auto-installed, entrypoint runs migrate+collectstatic,
docs/deployment.md) and trusts the agent's judgment. Dropped the now-
redundant Source Of Truth section.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-09-03 14:32:39 +01:00
..
cloud_agent_deploy.md Fix healthcheck + verify commands; reframe deploy runbook for a capable agent 2026-09-03 14:32:39 +01:00
docker-compose.yml Fix healthcheck + verify commands; reframe deploy runbook for a capable agent 2026-09-03 14:32:39 +01:00
Dockerfile Initial public commit 2026-09-01 21:55:02 +01:00
entrypoint.sh Initial public commit 2026-09-01 21:55:02 +01:00
env.example Close out issue 001: document CSRF/reverse-proxy requirement 2026-09-02 12:28:41 +01:00