NGINX Introduces Native Support for ACME Protocol  – NGINX Community Blog
blog.nginx.org
  • TheBigRoomXXL@leminal.spaceEnglish
    1·
    3 days ago

    FINALLY! Caddy has been doing it for years! I still prefere caddy overall but it’s nice to have as we don’t always choose the stack we work with.

    • pierAEnglish
      2·
      19 hours ago

      Even though I’ve been using traefik and caddy more lately, I appreciate that nginx has finally woken up :)

      • Elvith Ma'for@feddit.orgEnglish
        1·
        3 days 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.