victory

joined 2 years ago
[–] victory@lemmy.sdf.org 6 points 1 day ago* (last edited 1 day ago)

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)

[–] victory@lemmy.sdf.org 1 points 1 day ago (1 children)

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?

[–] victory@lemmy.sdf.org 1 points 1 day ago (2 children)

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?

[–] victory@lemmy.sdf.org 2 points 1 day ago (2 children)

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.

 

I'm thinking of expanding my homelab to support running some paid SaaS projects out of my house, and so I need to start thinking about uptime guarantees.

I want to set up a cluster where every service lives on at least two machines, so that no single machine dying can take a service down. The problem is the reverse proxy: the router still has to point port 443 at a single fixed IP address running Caddy, and that machine will always be a single point of failure. How would I go about running two or more reverse proxy servers with failover?

I'm guessing the answer has something to do with the router, and possibly getting a more advanced router or running an actual OS on the router that can handle failover. But at that point the router is a single point of failure! And yes, that's unavoidable... but I'm reasonably confident that the unmodified commodity router I've used for years is unlikely to spontaneously die, whereas I've had very bad luck with cheap fanless and single-board computers, so anything I buy to use as an advanced router is just a new SPOF and I might as well have used it for the reverse proxy.

[–] victory@lemmy.sdf.org 1 points 4 months ago

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.