traefik-kop
varnish-towncrier
traefik-kop | varnish-towncrier | |
---|---|---|
7 | 1 | |
124 | 23 | |
9.7% | - | |
5.3 | 0.0 | |
7 months ago | over 1 year 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
varnish-towncrier
-
How to create a full page cache within a CMS?
Having said that, varnish is an excellent tool for these situations and it also works well if you decide to use a CDN later on. We use the combination of varnish (caching for dynamic content) and Cloudflare (caching for static assets) in a couple of production environments and using the relatively recent CDN-Cache-Control headers it's finally pretty easy to separate cache control headers of various different links in your proxy chain. Be aware that cache tagging requires an additional module (xkey vmod) which isn't always shipped with varnish packages. To help with cache invalidations you can also use tools like Varnish Broadcaster (commercial) or (shameless plug) varnish-towncrier which decouples cache invalidation calls from varnish and doesn't require your application to directly talk to each varnish instance.
What are some alternatives?
traefik-modsecurity-plugin - Traefik plugin to proxy requests to owasp/modsecurity-crs:apache container
kube-httpcache - Varnish Reverse Proxy on Kubernetes
postgres-and-redis - 🗄 PostgreSQL + Redis. Self-Hosted. Docker + Traefik + HTTPS.
lfu-redis - LFU Redis implements LFU Cache algorithm using Redis as data storage
richardsoper.me - My Traefik V2 stack.
cache - Mango Cache 🥠- Partial implementation of Guava Cache in Go (golang).
TraefikKobling - A dynamic Traefik-to-Traefik discovery agent
varnish-modules - Collection of Varnish Cache modules (vmods) by Varnish Software
authelia - The Single Sign-On Multi-Factor portal for web apps
k3d - Little helper to run CNCF's k3s in Docker [Moved to: https://github.com/k3d-io/k3d]
registrator - Service registry bridge for Docker with pluggable adapters
traefik-ondemand-plugin - Traefik plugin to scale containers on demand