News for hackers. Stuff that matters.
Re:A first look at Aperture by Tailscale (private alpha) by SSLy on Tuesday January 27, 2026 @02:19PM (#46784953)
unrelated, but what's the path of least resistance to expose a couple of localhost-bound services to the tailnet, ideally with each having own hostname entry as the browser sees it?

they're not containerised, just plain old daemons.

Re:A first look at Aperture by Tailscale (private alpha) by timwis on Tuesday January 27, 2026 @02:27PM (#46785097)
This should work out of the box with Magic DNS (part of tailscale features). If machine A is named larrys-laptop and is running a service on :8080, then from sandras-laptop just navigate to http://larrys-laptop:8080 and it should work, provided both machines are on the same tailnet.
Re:A first look at Aperture by Tailscale (private alpha) by JayWS on Tuesday January 27, 2026 @02:38PM (#46785277)
https://tailscale.com/kb/1552/tailscale-services

Tailscale services will do that. You can do the proxying with tailscale serve, services gives you the MagicDNS name and virtual IP address bound to it.

Re:A first look at Aperture by Tailscale (private alpha) by SSLy on Tuesday January 27, 2026 @03:18PM (#46785901)
oh, that indeed worked. cheers!
Re:A first look at Aperture by Tailscale (private alpha) by lkosewsk on Tuesday January 27, 2026 @02:25PM (#46785063)
Give Tailscale serve a shot (https://tailscale.com/kb/1312/serve).

*edited; I initially pointed to Funnel which would be used for sharing outside your tailnet.