> I saw the "Install in the Cloud" option > ... > Unfortunately any church that wants to use this is going to need > someone technical enough to handle t

> I saw the "Install in the Cloud" option > ... > Unfortunately any church that wants to use this is going to need > someone technical enough to handle the installation themselves. I thought it would be awesome if that button would actually (eventually) result in setting up a droplet and installing the software for me. I think sandstorm[0] is going into that direction. I guess one tricky part of such infrastructure would be maintenance. Optimally, a user could spin up a "church.io"-drop (or e.g. "smtp/imap stack + $antispam + mailpile"-drop) and never have to care about any updates. providers can offer subscriptions for regular (curated) updates of each "drop". With such infrastructure in place, the curch-community could click said button, follow through some dialogs, enter a CC and 5 minutes later have their own instance + domain. timmorgan gets paid per install by the infrastructure provider (who profits on the long run through subscription-fees). I think the concepts of unikernels and clive[1] fit well into this picture, by exposing a more concise resource/environment API to the developer and easing deployment (which would be a nice thing, even without the picture painted above). [0] https://sandstorm.io/ https://sandstorm.io/ [1] http://lsub.org/ls/clive.html http://lsub.org/ls/clive.html