This is not the first contentious decision for caddy, and it does already have a fork: https://github.com/WedgeServer/wedge https://github.com/WedgeServer/wedge

This is not the first contentious decision for caddy, and it does already have a fork: https://github.com/WedgeServer/wedge https://github.com/WedgeServer/wedge On top of that, "fast, automatic TLS HTTP2 capable web server" is not some complex feat in Go. HTTP2 is already baked into the stdlib, and you can add automatic TLS via LE in a few lines of code: https://godoc.org/golang.org/x/crypto/acme/autocert https://godoc.org/golang.org/x/crypto/acme/autocert. A few alternatives: https://github.com/labstack/armor https://github.com/labstack/armor https://github.com/containous/traefik https://github.com/containous/traefik