Come on and fight me…

I just tried out caddy for the first time and found it to be fantastic, I have used both Traefik and Nginx Proxy Manager extensively and although they were both great, the simplicity of the Caddfilr is fantastic. With a few snippets configured, I can add a host with a single line that just defines the port and url, it’s like magic.

Has anyone got any known traps ( or tips) with caddy to make it useful.

The issues I have had previously with Traefik were the need to have multiplelines to configure it (and configure the host and router separately), and the difference between local docker services ( I do like using labels to configure, but with lots of services it gets a bit fragmented and difficult toanahe) and remote services ( had to use the file config).

With NPM, I find using the GUI to configure the servers difficult ( and challenging to keep consistent ) and I had a time that it forgot something ( can’t remember if it was certificates or something else ) and that was the straw that broke the camel’s back for me.

Anyway, currently I am happy with caddy and am not planning on replacing it (at least for a month or two :D ). It would be nice if there was a GUI, but no big drama honestly, and the text config is great.

  • karlthemailmanEnglish
    2·
    2 years ago

    Completely a personal preference, but this is one reason I prefer caddy. I like to keep the configs separate and not clutter up my compose files.

    It means I need to update two things when adding a new service (a compose file plus my caddy file), but I like the separation of concerns.

    It also makes my proxy config consistent for all services, regardless of whether that run in docket or elsewhere.

    • Edo78@feddit.itEnglish
      1·
      2 years ago

      I just use dockerized service and I plan to move to k8s so I don’t have (nor plan to) deal with anything besides dockerized services

      • karlthemailmanEnglish
        2·
        2 years ago

        Yeah, then I can see the appeal of keeping everything in the same configs.

    • lckdscl [they/them]@whiskers.bim.boatsEnglish
      1·
      2 years ago

      I like to keep the configs separate and not clutter up my compose files.

      You can do that with Traefik, I have all my reverse proxy config in a file that hot reloads by Traefik dynamically, so I don’t even have to restart Traefik, or even the compose files (that’s the problem with Traefik labels), just run compose, add service to said dynamic file, save, and the website is now reachable on the browser.