all 14 comments

sorted by: hot top controversial new old
[–] 14 points 1 year ago* (last edited 1 year ago) (1 child)

Hold off on this one if you use the official docker container.

This update has some broken dependencies the prevent it from starting correctly: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4606

  • source
  • hideshow 1 child comment
  • [+] 1 point 1 year ago (11 children)
  • [–] 1 point 1 year ago (8 children)

    I'm an old school nginx pro. So I keep using nginx for reverse proxies because it's what I know. What does caddy have to offer (or traefik is anyone wants to jump in)? Are they just optimized for this function and more modern?

  • source
  • parent
  • hideshow 8 child comments
  • [–] [S] 1 point 1 year ago (2 children)

    Why not Traefik as reverse proxy?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 year ago

    What they're asking is why Traefik/Caddy and not nginx? Do they offer anything that nginx doesn't? Nginx is pretty tried and true and honestly, in this space, I personally prefer tried and true over new and shiney unless new and shiney offers something I need that old faithful doesn't.

    To be fair, I was an Apache hold out for a looong time until I accepted my lord and savior nginx into my heart.

  • source
  • parent
  • [–] 3 points 1 year ago

    Configuration is much easier, e.g. this is the full config you need to expose nextcloud on nextcloud.example.com (assuming caddy can reach nextcloud using the hostname nextcloud)

    nextcloud.example.com {
            reverse_proxy nextcloud
    }
    

    Comparing that to ngnix configs that need a template for each different service (although to be fair they're mostly the same).

  • source
  • parent