[chef] Re: Re: Re: Puppet vs Chef

[Tim Uckun < >]

> By the way, it was always my intention to write a follow-up piece
> called something like '10 Great Things About Chef' - presenting the
> flipside of some of the arguments I've made here (some people prefer
> Ruby to a weird DSL that Luke made up, for example). Also, things Chef
> can do that Puppet can't. If anyone wants to email me with points for
> this article, I'll be very pleased to hear from you :)

You may also want to write an article about automateit. It's pretty
different than puppet and is sort of like chef solo but like chef it's
"just ruby". Unlike chef it imposes no structure on you, it's super
lightweight, it has no server (you have to figure out how you are
going to get your code to the machine yourself).

I quite like it.  Even if you don't want to use it for full blown
systems management it's an excellent "sanity check" tool to make sure
your application is properly setup and the dependencies are fully met.