NGINX Introduces Native Support for ACME Protocol  – NGINX Community Blog
blog.nginx.org
    • miss phant@lemmy.blahaj.zoneEnglish
      2·
      1 month ago

      I believe Let’s Encrypt only allows wildcard certs for DNS challenges so it’s not really in the scope of Nginx; but I haven’t used other web servers, do they implement that?

      Edit: Looked into Caddy, it seems to have a plugin system for DNS providers, that’s pretty slick. I can’t see that ever happening for Nginx they seem very opinionated in wanting to be unopinionated unfortunately. I’m still sad they rejected the PR to implement prefers-color-scheme for default error pages.

      • Elvith Ma'for@feddit.orgEnglish
        1·
        1 month ago

        For me it was usually that the config that I need to serve a site with TLS is quite short, there are sensible defaults and many things (e.g. websockets) just work without further declaration. That’s especially important if you want to host a container that has some lacking documentation about usage of reverse proxies, as most things “just work fine” for me.

        And using a simple include directive, you can even replicate ‘sites-available’ and ‘sites-enabled’ behaviour. My standard Caddyfile just sets up the log file format and location and basic Let Encrypt values. Then it includes /foo/bar/sites-available/*. Every deployment/container now has its own Caddyfile that just gets linked there.