ahmza
7d4f1668a6
Document running Caddy in front of the SWS origin for both deployment targets (Docker Compose on Gimli and the Kubernetes Pi cluster), with Caddy handling automatic HTTPS, compression, and security headers. Explains the layer separation: SWS serves static files + Cache-Control, Caddy owns TLS/compression/security headers (matching sws.toml where those are disabled). Caddyfile validated with 'caddy validate'.