this post was submitted on 21 Sep 2024
29 points (100.0% liked)
Mastodon
5257 readers
1 users here now
Decentralised and open source social network.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I understand Docker and know how to set up a Mastodon instance, but how do I run the web frontend separately from the backend?
And why would I even need Tailscale? Is there something I'm missing here?
I don't have a static IP at home, and even if I had one, I don't want to expose it to the internet.
Host on your home server with a Cloudflare tunnel. Cloudflare has a free tier that would suit your needs. It doesn't rely on static IP addresses, deals with all of the ssh certs, and won't expose your home IP address from incoming requests.
The backend workers make requests to other servers which would expose the IP address of those requests. You could use a VPN for the backend workers to protect those requests. But it's this really a concern? What risk vector are you protecting yourself from? Don't rely on security by obscurity. And even if a bad actor did get your IP address, you could just reboot your home router and get a new one.
I think you're over engineering a solution for unlikely risk vectors.
If you were using a hybrid approach you would need a solid networking solution between your VPS and home server. Tailscale makes that easy. The shared resources like reddis, postgres, S3 hosting, etc can all be on servers running Tailscale and will appear as local servers. You can solve this with your own VPN but Tailscale is solid and deals with non static IP addresses.
Tl;Dr, host at home, use Cloudflare, and don't worry about using a VPS (unless you need a high level of up time and have flaky Internet or power at home).