Hey everybody. I built this small Sinatra app because I wanted a simpler way for people to install my software OneBody[1] on DigitalOcean.<p>I'm not sure my little VPS will hold up under the strain of HN, but you can see the app in action at <a href="http://installer.71m.us" rel="nofollow">http://installer.71m.us</a> and even use it to install itself (how meta!) on DigitalOcean.<p>This uses the new MetaData[2] feature of the DO API to pass a config string to be processed by CloudConfig[3].<p>Once that is done, there is a small bit of code running on the VM to tell this app when the install is finished so you get a progress bar while you're waiting.<p>To be clear, DigitalOcean is doing all the real work -- this app simply acts as a hand-off between your app.yml config file on GitHub and the DigitalOcean API.<p>[1] <a href="https://github.com/churchio/onebody" rel="nofollow">https://github.com/churchio/onebody</a><p>[2] <a href="https://www.digitalocean.com/community/tutorials/an-introduction-to-droplet-metadata" rel="nofollow">https://www.digitalocean.com/community/tutorials/an-introduc...</a><p>[3] <a href="https://www.digitalocean.com/community/tutorials/an-introduction-to-cloud-config-scripting" rel="nofollow">https://www.digitalocean.com/community/tutorials/an-introduc...</a>
Love it! This is the exact type of thing that we hoped would come from providing the MetaData service.<p>Please submit it to our projects page so we can highlight it:<p><a href="https://www.digitalocean.com/community/projects" rel="nofollow">https://www.digitalocean.com/community/projects</a>
I'd be interested in adding this button once it gets offical support from DigitalOcean.<p>I added the Heroku Button[1] to a self-hosted OS app I wrote[2] and it seems to be useful (over 100 "recent deploys" per Heroku). It would be great if there was some affiliate commission as well - if someone signs up for a VPS to run an app, would be awesome to get a small kickback from DigitalOcean.<p>[1]: <a href="https://buttons.heroku.com/" rel="nofollow">https://buttons.heroku.com/</a><p>[2]: <a href="https://github.com/swanson/stringer" rel="nofollow">https://github.com/swanson/stringer</a>
<i>Something Something</i> WebIntents.<p>Why is "DigitalOcean" a choice made by the app, instead of by the user? Can there be a standard for this sort of installation metadata?
How are you planning on handling support for this going forward?<p>I have no specific need, I'm just always curious about how folks transition from, "I have a neat idea" to "I want my neat idea to work for most people".
same button for azure: <a href="http://www.bradygaster.com/post/the-deploy-to-azure-button" rel="nofollow">http://www.bradygaster.com/post/the-deploy-to-azure-button</a>
I have written something similar, it deploys Enferno (enferno.io) a flask based app on ubuntu (not necessarily digital ocean)<p>it's an ansible playbook that configures the server and installs all requirements, and sets up nginx, python for you.<p>whoever is interested, here is the source code:<p><a href="https://github.com/level09/enferno-ansible" rel="nofollow">https://github.com/level09/enferno-ansible</a>
Very neat. We did something very similar with the devo.ps button, allowing you to define configurable settings: <a href="http://devo.ps/blog/deploy-your-meteor-apps-on-digital-ocean-in-5-minutes/" rel="nofollow">http://devo.ps/blog/deploy-your-meteor-apps-on-digital-ocean...</a><p>We have yet to properly document the feature, but we've used it in a few places already.