Great work on v2!
Best way to get introduced is by forgetting to tag some docker server with the
maroilles tag and have it fail during the nightly pull update
On a more serious note: Just wanted to share some pain points that flared up from a docker user perspective:
- https://docs.traefik.io/migration/v1-to-v2/ is quite the TODO collection for a GA software release and it does require to migrate all acme.json files manually via an external tool into the same name?
- Most basic and daily stuff, like the default "entryPoints.http.redirect" directive which is the 3rd example in the 1.7 docs do not have any counterpart or is the RedirectScheme and is this per host or can the tests collide with other container labels?
- What happend to the simple "Basics" chapter? I just find myself between a huge info dump in "Getting Started" and "Config Discovery" which is a highly folded and nested document with so many side nodes and sub-configs with unintuitive Go-Templates forked into it that it becomes pure brain noise reading through it.
I'm not the ops guy, maintaining 100 swam servers and instances and stuff, just using it for some smaller projects but this project just feels a lot more complicated right now. Mixing all the default and easier stuff with docker compose on a static machine with notes about all the swarm specifics in the same document is so irritating. Maybe split the Docker chapter into Docker and Docker Swarm specific topics?
As a side question: I have some containers that use the old "traefik.frontend.auth.basic" stuff, putting those (or forgetting to convert them) into a traefik v2 proxy will not end up unprotected and will error out on startup correct?