Upgrade went mostly without a problem (had set more than one Hostname for a service before, seems to not work anymore lol), and i have a pretty large configuration that has grown over the past two years.
What i noticed is that it is quite a bit faster. Also the dashboard shows a little more information than before and the logs have colours now.
Juat an error due to the swarmRefresh setting in the traefik.yml.
Because I am not running in swarm mode it threw an error.
Oh well. Life and learn ¯_(ツ)_/¯
Yeah…I should be doing it but I am honestly too lazy to change my compose.
The only place I actually did it is my mongodb container bexause I know absolutely nothing about it.
At lwast I can rescue my traefik config :p
If I’m not doing anything fancy and just use it for basic reverse proxy stuff for my docker containers, would I need to change stuff in the configs? Most of the stuff mentioned in the migration guide is about tls.caOptional stuff, which I don’t believe I use.
Not necessarily just yaml — there are things yaml cannot do well, but even ignoring that, traefik can also use toml, or container labels — but rather, the entire concept of infrastructure as code is way better than GUIs. Infrastructure as code allows for much better linting, testing, and version controls thereby providing better stability and reproducibility.
Damn, same, nuked Traefik when v2 broke the setup I spent hours trying to figure out. I don’t think the concepts are overwhelming, but something is profoundly wrong with their documentation habits. Now someone in the comments here is saying v3 changes the way paths are read with regex? Lol, fuck Traefik, never again.
Add comment