Static HTML publishing compatibility page

Lifecycle: Compatibility. Last reviewed: 2026-07-17.

The former procedure on this URL copied website files directly into /opt/caddy/sites/ on ingress CT 103 and configured file_server there. That pattern is superseded because CT 103 is dedicated to DNS-facing ingress and TLS termination.

Use Publish a static website. The current pattern stores the generated artifact on CT 101, serves it read-only through a rootless Podman Caddy backend, and configures CT 103 only as a reverse proxy.

Existing sites that still use a CT 103 static root are historical exceptions. Inventory and migrate each site through an approved change; do not delete its files or route solely because this procedure changed.