Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Yes that's what you can use the tailscale subnet routing for - one some machine on the lan, that joins the tailnet, you configure it up to route to local subnets
Related question on the local subnets - I currently have Tailscale set up on my home server, phone, and laptop. However, it’s a little annoying that apps on my phone (like Synology Drive) should reference local IPs when on my LAN and then Tailscale IPs when outside of my home. Would you recommend setting up an alternate device at home (like Raspberry Pi) to function as a subnet router for Tailscale so that I can just use my local IPs no matter where I am? Is there any benefit to installing Tailscale on every device vs using a single subnet router for the entire home network?
You can try having the same hostname resolve on the lan to the local IP and only connect using that first part of the addess, having dns suffixes do the heavy lifting