[jetblackio]

That's unfortunate. I understand where you are coming from on making this absolutely as simple as possible for those who are maybe not so admin inclined, but I feel it's limiting to actual administrators/devops engineers, who are more than comfortable with traditional config management systems.

Personally as an administrator I want to be able to continue to use Ansible from the command line, but then grant access to my developers to a UI where they can easily spin up instances for temporary use.

That's just my use case. Otherwise, looks like a cool product. Good work.

[nodesocket]

Thanks. I agree it is a tricky balance. We want to empower everybody (especially less technical users) to interact with servers, yet be powerful enough for "neck beard" operations engineers. When in doubt, we always side with removing "power" features for simplicity. With that said, is creating recipes in a web interface and editor a deal killer for you?

[jetblackio]

Yes, I think it would be a deal breaker for me personally. For the one thing, there would be a bit of effort to migrate from any config management system (my background is Chef and Ansible) to straight bash scripts. Also, it doesn't allow for the modularity and reusability of scripts that these services grant you. In fact, if you really want to make this simple, adding support for config management as crucial. I can easily import a Chef cookbook, override a couple attributes and have a MySQL server up and running.

So ya, I think adding support for a config management system (my vote is Ansible) would make this 10x more useful.

[fps]

it seems from the demo that the script is simply executed on the server. There's no reason you couldn't build a commando.io "recipe" that just wraps ansible-playbook, although you should also look at ansible tower which does basically the same thing.

[joncooper]

Ansible Tower.