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
I'd rent one (small) VPS for $10 a month and split the bill. As far as I know that's how most people do it. It's going to have >99.6% uptime, a fast datacenter internet connection at some central location and runs on enterprise hardware... The Kubernetes approach adds a lot of complexity, you'll have your games disconnect anyway once it fails over as you can't migrate the IP addresses. And there will be some additional traffic between the locations to keep everything in sync. And 4x chance of some of the hardware failing and someone needs to fix it. Unless I'm mistaken about how Kubernetes works.
We don't want to pay for a VPS. We've been burned by that too often in the past were you go months paying for a minecraft server that noone is using after the first month
Fair enough. I mean I'd pay about 200€ a year in electricity to run 3 efficient computers. And my VPS is only 73€ and I never have to pay for replacement parts (SSDs, harddisks) which I had to replace at home. And then they have gigabit network, low latency, a proper IP address, it didn't fail yet so their reliability >99.6% seems to be correct. And that's all way better than what I have at home. So it's a no-brainer to go for that. But your calculation might be different.
I mean ultimately there is no harm in trying. If you have 3 old computers laying around, you might as well try setting up a kubernetes cluster. I think it's going to prove difficult to handle the IP addresses but I'm not an expert on high availability and gaming clients.
I'm pretty sure half the point of kubernetes is to have the server automatically reroute traffic when one node goes down
Good to hear. Are there specific example you could point me to? I'd like to learn more
But doesn't that require some software-defined networking or a special network setup? I'm pretty sure with the average home internet connection, you'll fail over to the replica at your friend's home. But that has an entirely different IP address and the game client will not handle that gracefully. It's going to disconnect. And you need to do some DNS as well to always point at the active server and forbid caching. In a datacenter or enterprise setting, sure. you'll just reroute the traffic and nobody will notice.