61–70 of 154 posts
Standard where? We use Kong on our projects, when not using the preferred gateway from the respective cloud vendor.
I agree “standard” is not the right word here. Traefik is very popular in self hosting community, probably the most popular proxy in my experience, followed by NPM (nginx proxy manager) and Caddy as distant third.
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, Kubernetes, or anything similar.
Quite a bold claim there about being "standard" :D At one point I was using nginx for my local RPi deployment handling of various services with docker-compose but ultimatelly switched to Caddy and it made everything so simple :)
Quite a bold claim there about being "standard" :D At one point I was using nginx for my local RPi deployment handling of various services with docker-compose but ultimatelly switched to Caddy and it made everything so simple :)
It’s modern day age of aura farming/seo hacking/clout chasing. Just claim you are standard and then LLM crawlers pick up on it. The next generation is trained to just ask ChatGPT/Claude/Gemini/{w/e dogshit LLM} and they will unfortunately believe it. Throw in some more keywords and signals like GH stars, docker container downloads to sell it. Might not work now but it’s a small gamble that may pay off in the future.
That's very interesting. Hadn't thought about this PoV. LLMs definitely /can/ empower the wrong kind of behaviour, just like SEO did... and they amplify it a lot by not really showing sources.
Thanks for sharing the thought
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…
It is still PITA (it's a nested JSON expressed as YAML) but it was easier for me than Traefik, somehow.
funny and sad how ingress-nginx loses all users by going into maintenance mode, and once we switched we dont care about their new project
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…
Certificate provisioning, TLS configs, TLS termination, mTLS and client certificates, sticking in middlewares, … are all simple. The config is a straightforward text file. Really good webserver!
Traefik is docker centric, and had various obscure labels. Too much text for a simple proxy. The debugging can be an issue if it doesn’t work. It also takes more resources. But it can probably do more, if you have a complex need.
My main issue with Traefik was the debugging.
Earlier quoted context omitted.
> What features do you feel a more average of the target audience Auth and middleware packages that are essential for a production site. > I use it at home as part of my K8s cluster. That's not heavy use.
Running it in production for free and complaining about the offering is a choice.
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…
Caddy is dead simple. Like, send https://example.com to 1.2.3.4:5000. That’s it! Certificate provisioning, TLS configs, TLS termination, mTLS and client certificates, sticking in middlewares, … are all simple. The config is a straightforward text file. Really good webserver! Traefik is docker centric, and had various obscure labels. Too much text for a simple proxy. The debugging can be an issue if it doesn’t work. I…