Did the creators of this use any of the tools in this domain? How does this compare to mcollective/capistrano/vlad the deployer/fabric/ssh and a for loop? It's a web app, how is that superior to something CLI based?
Thanks for the feedback. Right now, since Commando.io is so young I'll admit its not the most advanced tool. However, recipes are versioned and every execution and response is logged and stored for compliance and accountability.
When GitHub first was released, I am sure there was a skeptical group of developers who asked the same sort of questions.
Well, to repeat - how does this compare to tools in the domain? Why are you opting for a web interface driven approach over a command line interface?
Why are you opting to build the entire thing from scratch instead of using an existing orchestration tool and building an interface to that? Wouldn't that save you time and money?
I've most recently hammered on mcollective, and it can easily support multiple users, parallel requests, full auditing of all requests and responses, authorization, server discovery, etc. There's all your advanced features, already implemented.
In regards to the interface, our thought is this is what is currently missing from other tools in the domain. Imagine if GitHub had build just their API first without their interface. A fully RESTFul API with shell wrappers (node.js, python, perl) will come with time.
When GitHub first was released, I am sure there was a skeptical group of developers who asked the same sort of questions.
Also, Matriu asked for $250,000. :)