[{"data":1,"prerenderedAt":9},["ShallowReactive",2],{"post-\u002Fblog\u002Ftraeffik":3},{"path":4,"title":5,"description":6,"date":7,"rawbody":8},"\u002Fblog\u002Ftraeffik","Traefik","Dynamic routing that actually works","2025-11-28","---\ntitle: 'Traefik'\ndescription: 'Dynamic routing that actually works'\ndate: '2025-11-28'\n---\n\nConfiguring Nginx manually feels like doing taxes. You deploy a container, you want it accessible. Immediately.\n\n[Traefik](https:\u002F\u002Fgithub.com\u002Ftraefik\u002Ftraefik) solves this. It’s an edge router that listens to your infrastructure. It watches your Docker socket (or Kubernetes API), detects new services, and creates routes on the fly.\n\n> \"Træfik (pronounced traffic) is a modern HTTP reverse proxy and load balancer that makes deploying microservices easy.\"\n> — Traefik Docs\n\n### Why it matters\n\nStatic configuration is dead. If you are setting up complex networks or routing traffic through [custom ISP proxies](\u002Fblog\u002Fisp-proxy), you need a gateway that adapts instantly.\n\nTraefik handles the ingress automatically while you focus on where the traffic goes. It also handles Let's Encrypt certificates without you lifting a finger.\n\n### The Setup\n\nDon't overthink it. A simple `docker-compose` gets you running.\n\n```yaml\nversion: '3'\nservices:\n  traefik:\n    image: 'traefik:v2.10'\n    command:\n      - '--api.insecure=true'\n      - '--providers.docker=true'\n    ports:\n      - '80:80'\n      - '8080:8080'\n    volumes:\n      - '\u002Fvar\u002Frun\u002Fdocker.sock:\u002Fvar\u002Frun\u002Fdocker.sock:ro'\n```\n\nNow, just add labels to your other containers. Traefik does the rest.\n\nStop wasting time reloading configurations.\n",1783267423470]