Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I spent a bit of time at the beginning of the project evaluating the two and ended up choosing chef because it was going to be easier to use this way (aka build something on top of).

I will say that it was easier and far less confusing to get puppet up and running initially. There's definitely a bit that needs to be worked out in the chef documentation. The "Ruby"-ness of chef wasn't really a deciding factor as I can work with just about anything as long as it's reasonable.



I am slightly ashamed to admit that I'm still more into cfengine than either, and then writing personal scripts to install ~everything.


I'm a fan of whatever gets the job done. In the end it's still scripting just with fancier mechanisms to get the process started and report back.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: