4 ms·
Your logic assumes that Caddy's auto-HTTPS cannot be configured and must be self-contained, but that's not accurate. Caddy can be configured with traditional, m
by mholt 7y ago
Your logic assumes that Caddy's auto-HTTPS cannot be configured and must be self-contained, but that's not accurate. Caddy can be configured with traditional, manually-managed (or externally-managed) TLS certificates just like other web servers too, if you need that.
All we're saying with this project is, "There is a better way going forward, and we're solving that problem."
- notyourday 7y agoYou are presuming that as a designer of the Caddy you understand how the non-single-VM customers are running their infrastructure. Here's a typical problem of a distributed entry point system - network partitioning. * If your key/cert store relies on key servers being always accessible from everywhere, it simply won't work. * If your solution is to bake a key into a file system, then it is no better than existing nginx implementation. Basically, if you want your solution to be adopted, it needs to be significantly better than the entrenched ones.