Would be neat to pair this service or one like it with the "Deploy on Heroku"-type buttons/badges I've seen on github before. A "Run this container now" type thing.
There was a YC proposal by a couple of cofounders who wanted to start a business around this premise and had a working prototype, including WEB IDE integration for quick PR submissions.
I met with them about a year ago, thanks for reminding me to check in!
Actually you only need use your private key to sign a message to pay, which then triggers the deployment. I have an example, if you are so inclined: https://www.stackmonkey.com/demo/splunk/
If you are referring to Giant Swarm, yes, we have a few private deployments in production in Europe. If you are referring to the CI project, nah, it's just an example of what you can do! :)
"This container will be alive for next 15 minutes. If you would like to keep it running more than 15 minutes please contact us on Twitter."
- Changing 12 hours to 15 minutes, is the server overloaded?
We already receive a lot of interest but we just wanted to have more engagement on Twitter too :) We hit 300Mbps on our traffic and 30% on our CPU load. So, we still have more resources to serve. Also, our clusters are waiting to be spinned. Do you have any other recommendations to handle those requests and processes?
15 minutes seems reasonable to me. I thought the original 12 hours was too long - I was done with the container I spun up a few minutes after I started it.
I made a couple of things sort of like this, one I spent several months on. Another was simpler. Neither was finished since I needed to work eventually for money.
Here is the simpler one which is a backend for a barely started mobile front end.
I basically came to the conclusion that for scale simplicity and security I needed a new Digital Ocean VPS for each container so that's what I did. To make it faster you could sort of pool them ahead of time.
That one also has too many stars, interesting. I'll check it in detail. Did you apply for early access? If not, please do. We'd like to be in contact with you. Here is the link: http://goo.gl/forms/c9uNRsrsPq
Really great implementation. I was delighted to see that clicking on the 'Run Now' button immediately launched a container - no sign in, etc required.
I've been working on a similar idea for running docker containers on a cron schedule. I use them for data processing, and web crawling, but don't have a good way to manage their schedules / logs. Right now I run everything off a single box with a cron schedule for each one.
I schedule them so I can run a recurring task every day.
Examples:
1. Crawl a website, and store the data to a database - update every few hours.
2. Check a website for changes.
3. Process log data, and save it to another location.
Docker may be overkill for some of these, but it provides a simple way to launch a new task in a container with all dependencies installed. The overhead seems to be relatively small for starting a new container, so it's worth the overhead vs. configuring a machine to run the container.
Seams reasonable. I think it also can help to not have zombie processes after cronjobs. Well, then we'll definitely consider having scheduling. Thanks mate!
Interesting choice in building this atop DigitalOcean. Not that it's wrong by any means, but I'd be interested in hearing what process you took in choosing them. (just curiosity)
Wow, you are the first person who noticed that! :) We already had a couple of DigitalOcean servers running and wanted to add this one next to them. Do you have any recommendations? Why are you curious about it?
I've said this before and time and time again, but I LOVE what they're doing over at RunAbove (OVH incubated). I'm not affiliated by any means, just a very, very very very very happy customer. The performance is unmatched and the price is so competitive!
What are people planning on using this for?
Testing their own containers, or more testing things that rely on the services provided by existing published containers?
I'm torn. Your UX is about convenience, so probably expose a form for the MVP, so I can set an initial user and DB credentials for WordPress, for instance. I would probably implement it as JSON from the start though, then make it available when the REST API is ready.
I worked on it some more after doing a few try* sites, and open sourced a version [2] which could take any docker image name and do the same.
1: https://blog.docker.com/2013/07/try-rethinkdb-in-the-cloud-w...
2: http://github.com/keeb/any-saas