There is no universal API for Docker that would allow one to install "anywhere that has docker", at least as far as I know.
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.
I'm not sure this app would get official support from DO, since it's a bit hacky. I imagine DO would add their own install-button support at some point in the future (at least I hope so).
This app does set a referral cookie whenever someone chooses to install an app using it.
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?
This is a tool that scratches my own itch -- certainly not something I care to be the end-all of service-agnostic app installer.
There is also another project which is cloud-init [2] that defines an standard way of mounting the initial data, and provision the shh keys.
Cloud Formation is aws implementation of this and is quite good. You can create define a template of how your application should be deployed and parameters for the end user like Heroku button.
You can check a good example of these technologies on the coreos landing page [4].
[1]: http://en.m.wikipedia.org/wiki/OASIS_TOSCA https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=...
[2]: http://cloudinit.readthedocs.org/en/latest/
[3]: http://aws.amazon.com/cloudformation/
[4]: https://coreos.com
edit: ah, I see from other comment that there's apparently possibility of gaining some "cash" from DO for the ads: https://www.digitalocean.com/referral-program/ although seems only useful if one's using the DO platform himself (works as a discount).
Sorry, but we’re having trouble signing you in. We received a bad request.
I'm not sure my little VPS will hold up under the strain of HN, but you can see the app in action at http://installer.71m.us and even use it to install itself (how meta!) on DigitalOcean.
This uses the new MetaData[2] feature of the DO API to pass a config string to be processed by CloudConfig[3].
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.
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.
[1] https://github.com/churchio/onebody
[2] https://www.digitalocean.com/community/tutorials/an-introduc...
[3] https://www.digitalocean.com/community/tutorials/an-introduc...
But now what? I can't even SSH into it as I don't have the pw. I hit port 80 and all I get is the same "install it on DO page".
I thought it'd do a 1 click deployment, I'm stumped :(
ssh root@the-ipBut for a whole host of people, getting the app running quickly on a host they control is like magic.
[1] https://github.com/churchio/onebody/wiki/Manual-Installation
Please submit it to our projects page so we can highlight it:
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".
it's an ansible playbook that configures the server and installs all requirements, and sets up nginx, python for you.
whoever is interested, here is the source code:
We have yet to properly document the feature, but we've used it in a few places already.