[chef] Re: Standard Practices

[Ben Hartshorne < >]

A number of folks responded indicating a myriad of problems with having all the cookbooks in one repo.  I'd like to hear more about these problems.  So far (admittedly, without too many people working on the cookbooks) I've had no trouble keeping all the cookbooks in one big repo together.  Following the standard practice of branch/work/merge, unless we're actually working on the same part of the same cookbook at the same time (which would clearly have issues even if each cookbook was in its own repo), the merges all happen with no trouble. 

Could one of you that migrated from one-big-repo to tons-of-tiny-repos describe in more detail the issues you encountered? 

My other question is how you deal with having so many repositories.  When you want to refresh your local copy, I'm used to just doing a 'git pull'.  Instead do you have to 'for i in *; do pushd $i; git pull; popd; done' every time you want to get everything up to current?

Thanks,

-ben

On Wed, Mar 13, 2013 at 8: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