[chef] Re: Standard Practices

[Kevin Nuckolls < >]

I think it's an emerging best practice to go with having everything but cookbooks in your master git repo: environments, data bags, roles, etc. Then keep just all the cookbooks in their own repositories. You should look into how people are beginning to use the wrapper cookbook pattern and what berkshelf provides to tie everything together. After a year and a half of doing it all in one big repository and feeling the pain of it, I can unequivocally say that I think this is the future.

http://devopsanywhere.blogspot.com/2012/11/how-to-write-reusable-chef-cookbooks.html
http://berkshelf.com/
http://www.ustream.tv/recorded/27487546/highlight/309841

Best Regards,

-Kevin

On Wed, Mar 13, 2013 at 10:22 AM, Mark Pimentel < " target="_blank"> > wrote:

I just wanted to get a feeling for what standard practices people are following for managing chef cookbooks.

We will be moving to git internally and I would like to plan out the migration of our cookbooks to git.  What is the best practice for this layout?

One repo per cookbook? or all cookbooks in one repository?

How about databags, roles, environments?

Any feedback would be greatly appreciated.

--
Thanks,

Mark