Show HN: Switchboard – A mDNS based reverse proxy for personal infrastructure
1–10 of 38 posts
Re: Show HN: Switchboard – A mDNS based reverse proxy for personal infrastructure
#2Re: Show HN: Switchboard – A mDNS based reverse proxy for personal infrastructure
#3I’m in the process of building out a smallish home lab, with most things running in containers, and one of the things I wanted was dns for my internal things that Just Worked. It seems this is still harder than it needs to be. I started looking at Consul + Traefik, but the latest version of Traefik seems to have gotten significantly more complex for simple use cases. I’ve since started looking at Caddy, which seems f…
Re: Show HN: Switchboard – A mDNS based reverse proxy for personal infrastructure
#4I’m in the process of building out a smallish home lab, with most things running in containers, and one of the things I wanted was dns for my internal things that Just Worked. It seems this is still harder than it needs to be. I started looking at Consul + Traefik, but the latest version of Traefik seems to have gotten significantly more complex for simple use cases. I’ve since started looking at Caddy, which seems f…
Re: Show HN: Switchboard – A mDNS based reverse proxy for personal infrastructure
#5I’m in the process of building out a smallish home lab, with most things running in containers, and one of the things I wanted was dns for my internal things that Just Worked. It seems this is still harder than it needs to be. I started looking at Consul + Traefik, but the latest version of Traefik seems to have gotten significantly more complex for simple use cases. I’ve since started looking at Caddy, which seems f…
reverse_proxy localhost:8000
Re: Show HN: Switchboard – A mDNS based reverse proxy for personal infrastructure
#6Seems like the perfect thing for me (I run a stupid dual-traefik setup that does TLS SNI negotiation for me that I want to get rid of), but I can't figure out what is this.
Re: Show HN: Switchboard – A mDNS based reverse proxy for personal infrastructure
#7I’m in the process of building out a smallish home lab, with most things running in containers, and one of the things I wanted was dns for my internal things that Just Worked. It seems this is still harder than it needs to be. I started looking at Consul + Traefik, but the latest version of Traefik seems to have gotten significantly more complex for simple use cases. I’ve since started looking at Caddy, which seems f…
Re: Show HN: Switchboard – A mDNS based reverse proxy for personal infrastructure
#8I’m in the process of building out a smallish home lab, with most things running in containers, and one of the things I wanted was dns for my internal things that Just Worked. It seems this is still harder than it needs to be. I started looking at Consul + Traefik, but the latest version of Traefik seems to have gotten significantly more complex for simple use cases. I’ve since started looking at Caddy, which seems f…
I have been using it for years now for my personal stuff (almost all containers) and it's a breeze (the https part especially). I recently [0] added SSO for all my local stuff so I just have to login once and have access to everything.
[0] https://joshstrange.com/securing-your-self-hosted-apps-with-...
Re: Show HN: Switchboard – A mDNS based reverse proxy for personal infrastructure
#9Re: Show HN: Switchboard – A mDNS based reverse proxy for personal infrastructure
#10A little bit of docs would help. Not sure what a node is here, and what is mDNS doing. Seems like the perfect thing for me (I run a stupid dual-traefik setup that does TLS SNI negotiation for me that I want to get rid of), but I can't figure out what is this.
mDNS is just the method of communicating what traffic should be sent where. The "switchboard" listens for mDNS broadcasts that tell it what services want traffic routed to them under what conditions. A "node" (which was a bad choice of words) is the other side of that, a program broadcasting one of those mDNS resources (e.g. send traffic that's been sent to the domain "example.test" to this machine on port 8080)