I don’t know how you have implemented this, but on AWS we tend to set up an automatic snapshot every x-hours that expires (gets deleted) after y-days. If worse comes to happen, you resurrect the latest snapshot and you’re up and running. This isn’t a high stakes environment, so small levels of data loss might be acceptable to the community.

I’d be happy to look at and assist with your GitHub repository. Note that I am unable to make a specific time commitment at this point.

I did consider making the “business” aspect explicit in my list, but shied away from it, since with that comes “commercialism” and many mistake that within the context of Amateur Radio. For example, I’ve been told by “experts” that my podcast is a commercial enterprise and should be banned from local repeaters because I make an eBook available of the transcripts and in the past I had a “Donate” button on my website - no longer, thanks to the shenanigans by PayPal.

There is nothing wrong with “failure”. It’s a state, just like “on” or “off”. If it doesn’t do what you want, then you might call that state “failure”, but if it did exactly what you planned, then that might be called “success”, even if from the outside looking in, the two are identical, the instance is no longer responding. In other words, this is a matter of perspective and planning. Which is why we’re having this conversation in the first place :-)