Thanks for the overwhelming response - making the front page of HackerNews unexpectedly. DeployButton was our entry to RailsRumble this year, and it's a solution we created because we wanted something like this for ourselves for our own startup, Lizi.
Over the next few weeks, we'll be updating a few key issues that have been raised in these comments, including the ones about security.
We don't immediately accept that enterprises will jump to use DeployButton, but for a series of smaller consultancies, the security features we will offer will be more than enough.
Thanks again for the support - Sometimes I wish there was a "Whoops, we're not ready for HackerNews yet, don't taze me bro" break-the-glass button that puts us back on after a month's time.
I like the idea and you've got an interesting internal page, but your front page ("What if deploying your code...") is literally unusable on an iPhone and probably on other mobile platforms -- the button is not visible, nothing is clickable, and it can't be scrolled or resized. You might want to rethink that so as to capture the people who are browsing HN / TechCrunch / whatever while surfing on the bus on the go.
Sorry about this, a fix for this is coming too! From what I understand, we're not allowed to check in or "deploy" until the competition (judging) is complete, but its now on our list.
Thanks so much for your support!
Checking again, I see that there's a four or five pixel strip of red bottom center that is actually clickable, but it's not exactly obvious. Screenshot here: http://imgur.com/JWcaP
Dropbox let us set things up nicely, where we opt for only a single folder (Apps/DeployButton) and we can only see stuff you place directly inside.
The main appeal of DeployButton for me was to have a service I could easily connect to Campfire/Hipchat to script out deployments from there. It's not that deploying is "hard", it's that it's tedious and I believe should always done as a collaborative experience instead of solo.
More feedback greatly appreciated. Site and workers are already overloaded (we didnt anticipate an HN post). So apologies in advance.
I'm sure there's good reasoning behind wanting to give a non-technical user the rights to deploy code to servers, but I'm afraid I can't seem to conceive of them right now. Can you elaborate why you would want someone without the requisite technical skills deploying code?
Sure you can abstract copy from your codebase or markup, but that's not trivial or necessarily a benefit.
It's also nice for a consultant who manages many clients, which we included in the copy in other places.
Honest question - I'm wondering what I'm missing.
And yeah, security would be an issue for me. I would most likely set up a user just for DeployButton.
These kids need mentoring bad. Someone steer them to a worthwhile project please.
All that aside, I'd love to hear your worthwhile project ideas, Moe! email@example.com
I appreciate the support and heads up!
What about databases?
What about multiple code/DB versions and rollbacks?
What about rolling out to one data center and directing 1% of the traffic there?
What about fast P2P deployments?
DeployButton is just the trigger button, not the missile :)
At the very least, all of my projects can be developed on in a live testing environment after one step after check out and it works everywhere the toolchain works. It lowers barrier of entry for developers and for users that want or need to build from source.