3 ms·

I liked v1 a whole lot. I'm interested in v2, though I'm extremely skeptical of the additional complexity of the config adapter layer (https://caddyserver.com/

I liked v1 a whole lot. I'm interested in v2, though I'm extremely skeptical of the additional complexity of the config adapter layer (https://caddyserver.com/docs/config-adapters https://caddyserver.com/docs/config-adapters) - I'm more or less sold on having an internal JSON structure with a DSL on top of it (allowing dynamic/programatic config is really interesting), but the idea of having _multiple_ different DSLs or config syntax bindings for it seems a bit much. The biggest feature in Caddy 2, from what I can tell, is the new HTTP config API, and I'd love to see a practical example of what could be done with that.

francislavoie 6y ago
Caddyfile is the primary supported DSL. The rest are nearly 1:1 mappings to the internal JSON with some sugar, except for the nginx config adapter which is a bit special! For example jsonc provides JSON, but with comments. A few of those are third party maintained, and are plugins. They're listed on that page to point out what's possible. There's a tutorial for the API in the docs that should give you a good idea of what you can do: https://caddyserver.com/docs/api-tutorial https://caddyserver.com/docs/api-tutorial
mholt 6y ago
Don't worry about the "additional complexity" -- config adapters are modular, and only the Caddyfile adapter is baked into the standard modules. Just plug in the adapters you need. Caddy functionality can grow rather infinitely without bloat because of this. Some adapters are 1:1 translations so they are just a few lines of code: https://github.com/caddyserver/json5-adapter/blob/master/json5.go https://github.com/caddyserver/json5-adapter/blob/master/jso... True, the Caddyfile adapter is a bit of a beast because it is extensible itself -- but it's a lot cleaner and more flexible than the v1 implementation, where the Caddyfile was its native config syntax. Believe me, this is a big improvement. Anyway, you don't have to use the adapters if you don't want to. That's the beauty of it. More info on the architecture and config adapters: - https://caddyserver.com/docs/architecture https://caddyserver.com/docs/architecture - https://caddyserver.com/docs/config-adapters https://caddyserver.com/docs/config-adapters

francislavoie 6y ago

Caddyfile is the primary supported DSL. The rest are nearly 1:1 mappings to the internal JSON with some sugar, except for the nginx config adapter which is a bit special! For example jsonc provides JSON, but with comments. A few of those are third party maintained, and are plugins. They're listed on that page to point out what's possible. There's a tutorial for the API in the docs that should give you a good idea of what you can do: https://caddyserver.com/docs/api-tutorial https://caddyserver.com/docs/api-tutorial

mholt 6y ago

Don't worry about the "additional complexity" -- config adapters are modular, and only the Caddyfile adapter is baked into the standard modules. Just plug in the adapters you need. Caddy functionality can grow rather infinitely without bloat because of this. Some adapters are 1:1 translations so they are just a few lines of code: https://github.com/caddyserver/json5-adapter/blob/master/json5.go https://github.com/caddyserver/json5-adapter/blob/master/jso... True, the Caddyfile adapter is a bit of a beast because it is extensible itself -- but it's a lot cleaner and more flexible than the v1 implementation, where the Caddyfile was its native config syntax. Believe me, this is a big improvement. Anyway, you don't have to use the adapters if you don't want to. That's the beauty of it. More info on the architecture and config adapters: - https://caddyserver.com/docs/architecture https://caddyserver.com/docs/architecture - https://caddyserver.com/docs/config-adapters https://caddyserver.com/docs/config-adapters