[grocketeer]

> I do what you are describing for fun, but I would never recommend it for a business, even if it is reliable.

I appreciate your response and don't necessarily disagree. Could you tell me a little more about why you wouldn't recommend it for a business, even if it is reliable?

> To get around the reliability problems, I have the on-prem laptop environment update cloudflare entries with keep-alive timestamp messages. .. I then have a Google script that monitors the keepalive and if too much time has passed, a “failover” is done and everything that was running on-prem is spun up in digital ocean. The failover script completes by updating DNS and pointing to DO

This is a clever solution. Thank you for your thoughts!

[ratg13]

Yes, I wouldn’t recommend it for a business just due to the complexity of the setup and the necessary knowledge to keep it running.

If you’re able to document the setup properly and have multiple people that have intimate knowledge of your machinations.. then you are covered .. unfortunately most people do not cover these bases.

If you have built yourself into this process you will realize quickly that nobody else understands it, and you will have a hard time taking vacation (among other things)

Also you put the business at risk because you need to plan for what the company will do when you get hit by a bus.

For these reasons it’s generally more preferable to pay a premium to go with a standard solution as opposed to something you cobbled together to save small amounts of money.

[ttarr]

> and the necessary knowledge to keep it running.

This is why I self host, gaining knowledge is a pro not a con.

[warrenm]

self-hosting for yourself can be a sane decision

self-hosting for a business is RARELY sane :)