[chef] Re: RE: Single Repo vs Repo per cookbook


Chronological Thread 
  • From: Lamont Granquist < >
  • To:
  • Subject: [chef] Re: RE: Single Repo vs Repo per cookbook
  • Date: Tue, 14 Apr 2015 11:11:23 -0700

Title: RE: [chef] Single Repo vs Repo per cookbook
On 4/13/15 1:17 PM, Kevin Keane Subscription wrote:
" type="cite">


The problem with berkshelf is that you can specify a git repository as source per cookbook, but you can't really specify a git repository that contains multiple cookbooks.


Isn't that only a problem if you have multiple repos with multiple cookbooks?  If you've got one repo with all your role and wrapper cookbooks, and then peel off individual library cookbooks which are one-cookbook-per-repo then it should work okay and you can just use `path: ../some_cookbook` in the Berksfile for the internal dependencies of the monolithic repo, and avoid having the library cookbooks having deps back into your monolithic repo (which would smell like you're starting to create circular dependencies).

Berkshelf should work fine for this model as well.




Archive powered by MHonArc 2.6.16.

§