own-proxy decision, terraform provisioner, system diagram, gateway SSE notes, server-budget comment and roadmap 0.4.0 now use Caddy with ACME-managed TLS instead of nginx plus certbot
Own Caddy reverse proxy instead of Cloudflare Tunnel
The apex domain points straight at the home server; a Caddy reverse proxy installed by Terraform is the only entry.
decision
networking
caddy
terraform
stable
by
at
claude-code/claude-opus-5-5
2026-10-14T00:00:00Z
by
at
human:noel
2026-10-14T00:00:00Z
Decision
No tunnel, no managed entry service. A DNS A record points the apex domain at
the home server directly; Caddy (provisioned by Terraform) terminates HTTPS,
gets and renews certificates via its ACME client, and forwards to the gateway
Service.
Why
A managed tunnel outsources exactly the part Noel wants to learn: DNS, TLS,
proxies and what happens between a browser and a container.
No dependency on a third party. The entry path is Noel's own code and config.
Caddy on the same 4 GB server costs a few MB, well inside the budget.
Automatic HTTPS needs no certbot; the Caddyfile is about five lines.
Consequences
Inbound ports 80 and 443 must be reachable at the home server (router
port-forward, static IP or DDNS). This is a solved-but-open question — see
open questions.