What problem does it solve? It turns a local HTTP-only backend on a remote Linux server into a publicly trusted HTTPS endpoint by installing and configuring Caddy without Docker, handling certificate issuance, verification, and rollback. ## Core Features & Use Cases - Domain-first deployment: Uses your own domain with Let's Encrypt HTTP-01 automatic certificate issuance as the preferred path. - DuckDNS DNS-01 fallback: Switches to a plugin-enabled Caddy binary with DNS-01 challenge when no own domain is available or port 80/443 reachability is unstable, including a low-bandwidth local-download-then-upload binary transfer option. - Verification and rollback: Validates the Caddyfile, checks certificate issuer and validity via openssl, confirms health endpoint responses, and restores prior binaries and configs when reverting. - Use Case: You have a backend API listening on 127.0.0.1:39080 on a VPS and want a browser frontend on GitHub Pages to call it over trusted HTTPS at api.example.com. ## Quick Start Deploy Caddy as an HTTPS reverse proxy on my server at ssh user@host for domain api.example.com proxying to 127.0.0.1:39080 with Let's Encrypt, then verify the certificate and health endpoint.
