homelab/traefik
1
0
Fork 0
Code Activity

Compare commits

base: homelab:bebd988162a584bbfa169ccd85e45439dee69bd8
Branches Tags
homelab:mine
..
compare: homelab:b4ef1baf65f63b77cfe71a7121a16e5d7e99599e
Branches Tags
homelab:mine

3 commits
bebd988162 ... b4ef1baf65

Author SHA1 Message Date
Arthur K.
b4ef1baf65
feat: custom label shorthands 2025-06-11 15:25:54 +03:00
Arthur K.
c826cc97e6
feat: callbacks 2025-06-11 15:25:54 +03:00
Arthur K.
c69246d93e
chore: remove github for local deployments 2025-06-11 15:25:42 +03:00
1 changed files with 4 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

12
README.md
View file

@ -1,7 +1,3 @@
# My modified version of Traefik
slightly modified version of traefik, will be rebased on the latest tag from time to time
this version includes callbacks to external services on configuration update and custom docker label mappings
feel free to check out last 2 commits, they are like 100sloc together
<p align="center">
<picture>
@ -47,14 +43,14 @@ Pointing Traefik at your orchestrator should be the _only_ configuration step yo
Imagine that you have deployed a bunch of microservices with the help of an orchestrator (like Swarm or Kubernetes) or a service registry (like etcd or consul).
Now you want users to access these microservices, and you need a reverse proxy.
Traditional reverse-proxies require that you configure _each_ route that will connect paths and subdomains to _each_ microservice.
In an environment where you add, remove, kill, upgrade, or scale your services _many_ times a day, the task of keeping the routes up to date becomes tedious.
Traditional reverse-proxies require that you configure _each_ route that will connect paths and subdomains to _each_ microservice.
In an environment where you add, remove, kill, upgrade, or scale your services _many_ times a day, the task of keeping the routes up to date becomes tedious.
**This is when Traefik can help you!**
Traefik listens to your service registry/orchestrator API and instantly generates the routes so your microservices are connected to the outside world -- without further intervention from your part.
Traefik listens to your service registry/orchestrator API and instantly generates the routes so your microservices are connected to the outside world -- without further intervention from your part.
**Run Traefik and let it do the work for you!**
**Run Traefik and let it do the work for you!**
_(But if you'd rather configure some of your routes manually, Traefik supports that too!)_
![Architecture](docs/content/assets/img/traefik-architecture.png)