Selfhosted

39435 readers

5 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

[email protected]

Traefik tutorials? (self.selfhosted)

submitted 1 year ago by Still to c/[email protected]

14 comments fedilink hide all child comments

I'm migrating my server to a new server and wanna try something new. I've been using nginx to reverse proxy my stuff and I recently heard about traefik being able to read labels off docker containers. I've been googling around but I can't for the life of me figure out how to get the access to the dashboard without having insecure mode on.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 year ago (1 children)

by redeploying the stack

That's the point. With dynamic files you can add new Middleware or even route already exposed ports all on the fly. You're telling me you can change a docker label and keep your service running with 0 downtime?

If you've figured that out please share a link because my experience has been otherwise.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago)

Close enough to 0 downtime that it doesn't matter.

Deploy updated stack file to existing stack
existing services are updated
Traefik polls the docker socket and notices updated labels
???
Profit!

Seriously, you shouldn't need to put anything (outside of rules that you want to re-use [e.g. http->https middleware]) in the traefik dynamic configuration because each container/service in a docker stack will bring with it its own configuration. Your only 'dead time' is how long it takes Traefik to pick up the new dynamic configuration via either the docker or swarm providers, which is configurable but I've never had to touch because, even on production systems, it's been fine.