This is bullshit, I'm done with Caddy. It's burned me so many times. They keep shipping half broken shit like their HTTP/3 support that was enabled by default (currently broken in releases because it sends duplicate Content-Length headers)
I'm switching to Apache LMAO. It's gonna be 95% the speed of Nginx and they ship mod_md in their Docker images so it can handle fetching its own Acme certs
additionally Caddy's Prometheus metrics have been broken since their creation because they cause a serious performance impact when enabled and nobody seems to care enough to prioritize it
feels like Caddy itself is barely on life support, I can't imagine anyone is using it for super serious projects right now
@smortex I used it in prod for a project for a couple years because the plugins/modules for it provide some really nice functionality sometimes... we had a site that provided services on subdomains, but it was *.*.foo.com which a wildcard can't do, so it has to generate a certificate on-demand when the domain is accessed if it doesn't have one yet. I was able to use a module (certmagic) to let me store the certs on an S3 bucket so every server could have access to the same certificates
So in that respect it works pretty well, but their HTTP/3 support sucks and they have bugs like the metrics causing performance issues that have existed for years and nobody's fixed it...