Yeah I plan on doing a batch of updates this week and flesh out more of the content next week. Let me know what topics are of most interest to you and I'll prioritize those. Thanks!
Thanks for the response. While I haven't read the book yet and only briefly looked through it, I think the most important areas to cover are 'development process/workflow' and 'testing'. Opscode does a pretty good job of explaining how to actually write cookbooks and things like LWRPs, but the two areas I mentioned are rather fragmented on the web.
I've also heard about the idea of 'Library Cookbooks', and the idea of having a generic cookbook that you can include in an organization-specific cookbook seems very intriguing. If you are familiar with this concept, including it the book would be quite worthwhile.
Another area I would be very interested in is Chef Best Practices. I've gotten myself into quite a bit of trouble by putting way too much information in my roles, only to run into all sorts of trouble with versioning when working in multiple environments i.e, 'dev', 'test', 'prod'.
Anyway, thanks for putting in the effort to get a book out. Chef is a little starved in the way of accessible information (I shouldn't have to resort to IIRC multiple times per day to get questions answered). This is badly needed.
Thanks for this, you have the same concerns as I that prompted the book, which started out as the development of the "Chef Broiler Plate" https://github.com/jrobertfox/chef-broiler-plate because there were all these great tools, but no cohesive idea on how to integrate all of them.
I think i'll add a section that goes over the process as you say, because once the framework is set up you could
-create cookbook
-build tests
-write book
-verify quality
-test on vagrant
-version/promote
Sounds like we are on the same page exactly. That process sounds good. And if you are able to clearly lay out how all the various tools integrate in to a cohesive whole, you'll have solved a very big problem in the Chef community.
