Traefik's 10-year anniversary
traefik.io
Traefik's 10-year anniversary
1–10 of 154 posts
Re: Traefik's 10-year anniversary
#2Traefik's F/OSS projects are useless to me. Every single feature that I need to use is locked away in a closed source product.
Close to the same issue with Varnish Enterprise. Why would I pay for Varnish Enterprise if I can't even review or extend the source? Know what I have to do with Varnish's source once a quarter? I have to look at it. Because the documentation is non-existent. The closed source version is going to make my life objectively worse.
Aside from NGINX, Postgres, and memcached, I've had to patch every major piece of software in my stack at one point or another. I refuse to use any product that I can't fix myself.
It's current year, why are JWTs only supported in the closed source/enterprise versions of Varnish, NGINX, and Traefik?
I happily give $1,000/year to Django and lesser amounts to other projects that I depend on. Do you know how much I spend on projects that put features behind a closed source product? Zero. I will never pay for that.
Re: Traefik's 10-year anniversary
#3Was just taking a break from reading Traefik documentation - thank you for this amazing project.
Re: Traefik's 10-year anniversary
#4Traefik's F/OSS projects are useless to me. Every single feature that I need to use is locked away in a closed source product. Close to the same issue with Varnish Enterprise. Why would I pay for Varnish Enterprise if I can't even review or extend the source? Know what I have to do with Varnish's source once a quarter? I have to look at it. Because the documentation is non-existent. The closed source version is going…
I don’t think this is representative of the majority of traefik’s users. Most of us use it as an HTTP entrypoint for a container stack (docker compose, in my case) or for local development, and the FOSS version works great for that, with better dev tooling than anything else i’ve seen.
Re: Traefik's 10-year anniversary
#5I don't generally use/need Traefik. But the cheese shirt makes me unreasonably happy, and if it appeared for sale on some easily accessible site for a decent price, I'd very likely order one.
Re: Traefik's 10-year anniversary
#6Horrible read. That whole post is nothing but gratuitous self-importance. Just don't use llms for something like this... it just gets over the top really easy.
Re: Traefik's 10-year anniversary
#7[dead]
Re: Traefik's 10-year anniversary
#8Traefik's F/OSS projects are useless to me. Every single feature that I need to use is locked away in a closed source product. Close to the same issue with Varnish Enterprise. Why would I pay for Varnish Enterprise if I can't even review or extend the source? Know what I have to do with Varnish's source once a quarter? I have to look at it. Because the documentation is non-existent. The closed source version is going…
I don’t think this is representative of the majority of traefik’s users. Most of us use it as an HTTP entrypoint for a container stack (docker compose, in my case) or for local development, and the FOSS version works great for that, with better dev tooling than anything else i’ve seen.
I disagree. If you're a heavy Traefik user you're eventually going to need a feature that has been carefully omitted from the F/OSS projects.
Re: Traefik's 10-year anniversary
#9I never understood why folks use Traefik. HAProxy feels more configurable and resilient.
Re: Traefik's 10-year anniversary
#10Traefik's F/OSS projects are useless to me. Every single feature that I need to use is locked away in a closed source product. Close to the same issue with Varnish Enterprise. Why would I pay for Varnish Enterprise if I can't even review or extend the source? Know what I have to do with Varnish's source once a quarter? I have to look at it. Because the documentation is non-existent. The closed source version is going…
[dead]