peter f2f2a9c96b Close out issue 001: document CSRF/reverse-proxy requirement ... The app-side fix (CSRF_TRUSTED_ORIGINS, SECURE_PROXY_SSL_HEADER in settings.py) was already committed as d458cd3 after the first Cloud-VM-1 deployment hit "CSRF verification failed" on login behind Apache. This finishes the rest of that issue's checklist: documents DJANGO_CSRF_TRUSTED_ORIGINS in deploy/env.example, adds the required X-Forwarded-Proto header to the Apache/Caddy examples in cloud_agent_deploy.md (plus a checklist item that verifies via an actual login, not just an unauthenticated capabilities curl), and adds the same proxy-agnostic guidance to docs/deployment.md. Also introduces issues/, a tracked one-file-per-issue log for the project going forward. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>		2026-09-02 12:28:41 +01:00
..
cloud_agent_deploy.md	Close out issue 001: document CSRF/reverse-proxy requirement	2026-09-02 12:28:41 +01:00
docker-compose.yml	Fix backup step to follow the configurable data path (F1)	2026-09-01 22:45:18 +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