News for hackers. Stuff that matters.
Re:Fucking Shell Scripts by sdegutis on Friday March 14, 2014 @05:34PM (#7402065)
We're using Chef right now, and evaluating other options. They seem to either be between way too over-engineered, or not flexible enough, but nowhere in between. I'd love to see a tool like yours be brought to full maturity, then I think I'd love to use it.
Re:Fucking Shell Scripts by digisign on Friday March 14, 2014 @06:48PM (#7402516)
As I mentioned in another place above, if you'd like an alternative that is even simpler than ansible, yet still idempotent, try pave:

https://pypi.python.org/pypi/pave

https://bitbucket.org/mixmastamyk/pave

Re:Fucking Shell Scripts by frist45 on Friday March 14, 2014 @05:48PM (#7402187)
Other co-author here: I couldn't agree with you enough. We settled on Ansible, but have had our fair share of speed bumps along the way.
Re:Fucking Shell Scripts by mikegirouard on Friday March 14, 2014 @06:07PM (#7402311)
Out of pure curiosity, what makes Ansible the best choice for you?

For my team, I decided on Ansible because it was the simplest option (no agents to install, pure ssh).

Re:Fucking Shell Scripts by sdegutis on Friday March 14, 2014 @06:09PM (#7402325)
By the way, that's the same reason I'm investigating using Pallet[1].

[1]: http://palletops.com/

Re:Fucking Shell Scripts by frist45 on Friday March 14, 2014 @08:31PM (#7402891)
We were coming from Chef where no one knew what was going on. We were looking for something simpler. There wasn't really many other options unfortunately. We're not full-time devops people...hence much of our frustration.