3 ms·
I self host most of my own infra but the sharing problem is certainly present, can you elaborate on how traefik helps?
by corndoge 4y ago
I self host most of my own infra but the sharing problem is certainly present, can you elaborate on how traefik helps?
- imwillofficial 4y agoIt's made self hosting proxying very very easy. Worth a look.
- kodah 4y agoTraefik can listen on individual addresses on a machine, which lowers the barrier to making a chained ingress. If chained ingress doesn't make sense, think of how Kubernetes has a load balancer pointing at several nodes and each of those nodes run an ingress internally to route traffic across the private-to-the-node network. For instance, I didn't want my sharing URLs to enter directly on my home IP. I felt that would expose my house to an enumeration of vectors that I couldn't possibly control. I ended up creating a small server in digital ocean that runs Traefik on a public address with various public DNS records pointing at it. That instance of Traefik then points to my home servers Tailscale addresses. I actually go a step further by running Traefik on each server so that I can host multiple services on port 443 on each server, but this isn't absolutely necessary. Hopefully that all made sense!
- disqard 4y agoDid you mean Tailscale, or Tailwind? I'm interested in replicating your setup, so if you happen to have a blog post or some other HOWTO resource, that would be deeply appreciated. Thanks in advance!
- kodah 4y agoI meant Tailscale, thanks for that. I use both but I think one has a dominant weight in my autocorrect, lol. Check back here and I'll dump my docker-compose. That pretty much contains everything except the actual agent installation, which is a very minimal step.