111–120 of 154 posts
Usual tribal bollocks in the comments. Personally, I generally rock Apache but Traefik, Caddy, ngnix and co are all superb projects. If you are going to get tribal about web servers, I suggest you think really hard about your career choice. Use the tool that works for the job in hand.
I use Traefik for local development on daily basis, where I have to run double digit https services. It works, but it was a pain to set up. The documentation sucks ** and the config is confusing AF. I would never recommend this to anyone. If i will have to reinstall my computer one day, Traefik will not be welcomed back.
Earlier quoted context omitted.
My original comment probably wasn't clear enough, I meant to say that caddy doesn't support layer 4 TLS termination without third-party modules. For example, if I wanted a reverse proxy in front of a Gitea instance that would terminate and route TCP packets to/from port 22... this is something Traefik can do out of the box.
We plan to move layer4 into the standard Caddy distribution eventually. We're still stabilizing it, and once we're happy with it (and have the time and energy to) we'll bring it in.
I use Traefik for local development on daily basis, where I have to run double digit https services. It works, but it was a pain to set up. The documentation sucks ** and the config is confusing AF. I would never recommend this to anyone. If i will have to reinstall my computer one day, Traefik will not be welcomed back.
Nginx which they used before works much better. And these days I use caddy on everything else. That really shines.
Earlier quoted context omitted.
I use caddy similarly, but it's a pretty straight forward setup.
As a self-hosting noob, I never got traefik to work properly, then caddy just worked and has been working since.
Earlier quoted context omitted.
We plan to move layer4 into the standard Caddy distribution eventually. We're still stabilizing it, and once we're happy with it (and have the time and energy to) we'll bring it in.
Exciting! Looking forward to it. I end up needing xcaddy for a few other modules so it's not that big of a deal, but I always feel better using first-party functionality over relying on third-party modules.
So much hate for Traefik here. I don't get it. I personally use it and find it amazing, but I read elsewhere that their enterprise offering is prohibitively expensive. I wish them to succeed, Traefik has been one of my favorite choices for Kubernetes for a long time now :)
If you can't get the basics right, you stay at the kids table forever.
So much hate for Traefik here. I don't get it. I personally use it and find it amazing, but I read elsewhere that their enterprise offering is prohibitively expensive. I wish them to succeed, Traefik has been one of my favorite choices for Kubernetes for a long time now :)
They consider caching and TLS to be enterprise features. If you can't get the basics right, you stay at the kids table forever.
There's a lot of mentions to Caddy here. Haven't used it as, back in the day, there was something funny about its license and binary distribution. AFAIK that's not a problem anymore, isn't it? From people that migrated from Traefik to Caddy... What are the main differences? Anything you really miss? I use Traefik in a bunch of small deployments, sometimes pointing to Docker stuff, sometimes outside of Docker, Kuberne…
Also iirc not all such functionality is actually available when configuring via Caddyfile so it can be confusing if you expect that and don't realize you need to switch to json/yaml configuration to do what you want. A little remniscient of the Traefik static/dynamic confusion ;)
All good, just things that can be different than what you are used to and expect.