Web / Caddy Server Interview questions
What is the difference between the Caddyfile and JSON config format?
| Aspect | Caddyfile | JSON |
| Readability | Concise, directive-based, easy to scan | Verbose, deeply nested objects |
| Feature coverage | Covers common cases; some niche module options need JSON | Exposes every module option Caddy supports |
| Loading | Adapted to JSON at startup/reload via a config adapter | Loaded directly, no adaptation step |
| Partial updates | Whole file is reloaded | Individual JSON paths can be patched via the admin API |
| Best for | Hand-written configs, small-to-medium sites | Programmatic generation, automation pipelines |
In practice, most teams write Caddyfiles for day-to-day maintenance and only reach for direct JSON edits - typically through the admin API - when they need to patch a single route without reloading the whole configuration, or when a feature genuinely has no Caddyfile shorthand yet.
Which format allows patching a single config path without reloading everything?
The Caddyfile's main strength compared to JSON is:
More Related questions...
