What problem does it solve?
Prevents production Caddyfiles from shipping with common security, reliability, and TLS mistakes that turn “it works” into an unsafe deployment.
Core Features & Use Cases
- Production Caddyfile guardrails: Ensures global options (email + admin off), safe defaults, and correct structure (one site block per domain).
- Secure HTTPS and TLS discipline: Avoids ACME staging leaks, requires mandatory email for ACME, and manages on_demand TLS with tenant validation.
- Operational hardening: Adds security header packs, structured JSON logging, reverse_proxy health checks, rate limiting patterns, and safe file_server usage.
Quick Start
Ask the agent to write a production-ready Caddyfile for your domains using forge-caddy’s rules, including global email/admin off, security headers, reverse_proxy health checks, and hardened logging.