I get it, and I’ve seen this response other places I’ve asked about this too. But a license agreement can just offer refunds for downtime, it doesn’t have to promise any specific amount of availability. For small, cheap, experimental subscription apps, that should be enough; it’s not like I’m planning on selling software to businesses or hosting anything that users would store critically important data in. The difference in cost between home servers and cloud hosting is MASSIVE. It’s the difference between being able to make a small profit on small monthly subscriptions, versus losing hundreds or thousands per month until subscriber numbers go up.

(also fwiw this entire plan is dependent on getting fiber internet, which should be available in my area soon; without fiber it would be impractical to run something like this from home)

Already considering using Kube, though I haven’t read much about it yet. Does it support this specific use case (making multiple servers share a single LAN IP with failover), in a way that an ordinary router can use that IP without special configuration?

Looking into this a little, it might be what I need. The documentation I’ve found on this says it uses VRRP, which creates a “virtual” IP address; will that be different from the machine’s own IP address? And will an ordinary router be able to forward a port to this kind of virtual IP address without any special configuration?

I don’t think this is it. The router doesn’t know anything about DNS, it only knows “this port goes to this IP address”. It seems like I either need multiple devices sharing an IP address or router software that inherently supports load balancing.

Dead Cells. I’ve been stuck on 3BC for years, but someday I’ll beat it! Someday…

I was wondering the same thing, I wanted to add JSON Feed support to an app I’m writing but couldn’t find any examples of it in the wild, and Google was no help. Good to know that NPR has one, though.