4 ms·
I'm not the GP, but I've had a similar experience, with the Caddy docs seeming good for simple configurations, but lacking for more complex ones. I last setup
by GordonS 4y ago
I'm not the GP, but I've had a similar experience, with the Caddy docs seeming good for simple configurations, but lacking for more complex ones.
I last setup a Caddy config maybe 6-
9 months ago, and everything related to client certificates was either scantily documented, wrongly documented, or not documented at all. It might be I got unlucky, as some of the client cert features were fairly new, but it wasn't a great experience.
Still, I much prefer Caddy's config system to Nginx or HAProxy.
Oh, something else I'd really love to see are more fully-featured example configs, as it can be hard to know how to start sometimes.
- gunapologist99 4y agoI agree completely. Fully-featured examples would be extremely helpful, especially with things like proxying to different servers for different paths and domains, static file serving set up differently for different paths and domains, various plugin setups, etc.
- mholt 4y agoOh, just saw this. You wrote your comment while I wrote mine. If you can enumerate specifically what you want to see, please submit it to our issue tracker: https://github.com/caddyserver/website https://github.com/caddyserver/website Generally we encourage examples in our community wiki though: https://caddy.community/c/wiki/13 https://caddy.community/c/wiki/13 -- much easier to maintain that way.
- mholt 4y agoExamples of "fully-featured" what though? The more features you add, the more combinations of ways to configure things there are. The problem with "fully-featured" examples is that people copy and paste instead of learn how the software works. I'd rather our user base be skilled crafting configuration. Generally we recommend that big examples go into our wiki: https://caddy.community/c/wiki/13 https://caddy.community/c/wiki/13