Using Traefik.io with your local docker environments
summary
Shows how Traefik.io becomes a local Docker reverse proxy that removes manual port mapping by using Docker Compose labels to publish service names and ports so multiple projects run concurrently without port clashes. Traefik auto-detects containers, provides a web UI listing routes and chosen ports, and requires Traefik and services on the same Docker network. Notes: running host Apache can conflict unless Traefik is bound to 127.0.0.2, and use a dnsmasq rule for .docker.localhost so browsers like Firefox resolve the names.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:45Local dev environment pain
- 2:34Discovering Traefik
- 3:34How Traefik works
- 5:00Setting up Traefik
- 6:05Traefik limitations
- 7:52Fixing host file issues
- 9:00Q&A
related talks
31mIntroduction to Traefik
28mMulti-Container Applications with Docker Compose
49mDocker Compose: From Localhost to the Cloud
35mMake Load-Balancing Great Again with !
30mSimplify All the Things with Docker Compose
26mRunning an AWS Stack on Your Local Machine
34mTest Environments Management with
21mMaking Docker Actually Work
