traefik-kop
registrator
traefik-kop | registrator | |
---|---|---|
7 | 2 | |
124 | 4,655 | |
9.7% | 0.0% | |
5.3 | 1.6 | |
7 months ago | 17 days ago | |
Go | Go | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
traefik-kop
-
Traefik Kobling: a Traefik-to-Traefik discovery agent!
Traefik gives you a lot of options to accomplish this, you can use docker swarm, move to kubernetes or use any of their discovery providers. These options were rather complicated solutions for what I needed, so I decided to look around for other alternatives. Here I found Traefik-Kop, but it I still had to do a lot of manual work and open a different port for each container I wanted to be accesible through my reverse proxy.
- Can an already running Traefik container on a network act as revesre proxy for co tainers on another network
-
Traefik vs NPM vs alternative for multiple machines
The obvious solution is docker swarm/kubernetes, but if you don't want to go all the way there yet I can really recommend traefik kop. Very simple to setup, you just add a redis service next to the traefik instance and set it up as a provider, then you run traefik kop on every other machine, pointed at that redis service. Traefik kop will discover docker services on the machine and write everything to redis and it'll get picked up ny traefik. Worked like a charm!
-
Routing traffic from another machine
Maybe this can help you https://github.com/jittering/traefik-kop
- Running traefik with multiple docker hosts
- New tool: traefik-kop - a discovery agent for non-swarm/k8s docker clusters
- traefik-kop: a dynamic docker->redis->traefik discovery agent
registrator
-
Traefik Kobling: a Traefik-to-Traefik discovery agent!
Had the same problem recently, and was close to building a tool like yours. But I discovered Registrator. I added a small Consul instance and the consul provider configuration to traefik. Registrator ( https://github.com/gliderlabs/registrator ) automatically registers new docker services on the second maschine. Stopped services are automatically unregistered. Had to cross build Registrator for arm64, but this was simple using Docker BuildX.
- Nomad vs. Kubernetes
What are some alternatives?
traefik-modsecurity-plugin - Traefik plugin to proxy requests to owasp/modsecurity-crs:apache container
kubernetes-the-hard-way - Bootstrap Kubernetes the hard way. No scripts.
postgres-and-redis - 🗄 PostgreSQL + Redis. Self-Hosted. Docker + Traefik + HTTPS.
nomad-pack
richardsoper.me - My Traefik V2 stack.
containerpilot - A service for autodiscovery and configuration of applications running in containers
varnish-towncrier - Distribute cache invalidation requests to a fleet of varnish instances.
containerpilot - A service for autodiscovery and configuration of applications running in containers [Moved to: https://github.com/TritonDataCenter/containerpilot]
TraefikKobling - A dynamic Traefik-to-Traefik discovery agent
authelia - The Single Sign-On Multi-Factor portal for web apps
thruster