Well Traefik just upgraded to v3 and broke all existing legacy syntax with v2.
I'm sure there's some good technical reasoning behind such a move but as a user this is absolutely a horrible experience. There's a flag to enable v2 syntax mode, but you know what there isn’t? A single one pager saying if you have X in v2, you need Y in v3.
I don't want to have to go spelunking for hours figuring out your new way of doing things just to get back to where I was yesterday.
I have over 20 instances of traefik deployed all over the place and this is going to be a big time sink. So, thanks? I guess?
I'm just trying to imagine a world where nginx or haproxy deliberately break ALL existing deployments. Total madness.
@ironicbadger I was an haproxy guy, but I've recently found a lot of success in using NixOS's declarative nginx configs + acme wildcard certificates. I don't have the config posted anywhere, but let me know if you're interested and I'll share it out!
Nix and NixOS users and experts: can you please explain to me why this 20+ year old technology has become the new hot thing in the last few years? I understand that we're dealing with interesting tech here, but I'd like to hear what's different now/recently.
@JoeRess I found it because I had new hardware and needed bleeding edge kernels. I've always been a Fedora and Ubuntu guy, I like stability and didn't want to learn Arch. In NixOS using the latest upstream kernel is a single line in the config, and it's never broken.
