Caddy does the same job as Nginx but follows a different philosophy: its defaults are already sensible for a static site, compression and caching included, so it serves correctly before you open any configuration file. In exchange it offers less room for deep tuning than Nginx.
What you would use it for
- Get a static site online as fast as possible without learning a web server config syntax.
- Sites with many CSS, JS and image files — compression and caching are on by default, nothing to tune.
- When you want a static server whose defaults are not the thing you have to fix first.
What Keenrig handles for you
- Pinned by digest, the same mechanism as every other catalog entry.
- Domain and certificate are handled by Keenrig's gateway — Caddy here only serves files, it does not obtain its own certificate.
- Health checked at `/`, rebuilt automatically if the container dies.
- Needs 64 MB of memory.
What it does not do. Caddy has excellent automatic HTTPS, but inside Keenrig that job belongs to the platform gateway, not the app. If you are installing this entry for Caddy's auto-HTTPS specifically, that is not what you get here.