[chef] Re: Re: Berkshelf with chef-repo: am I doing it right?

[Joshua Timberman < >]

I wrote a blog post awhile back[1] about my own personal chef-repo
conversion to use Berkshelf. The information is not all still 100%
relevant/accurate given the entropy of tool development and my
personal use patterns, but it's pretty close.

I still have a ./cookbooks directory, because I don't see a reason to
publish and manage 20+ additional cookbook repositories, especially
private ones. The main difference between the post and now is have a
helper method like this in the Berksfile:

def internal_cookbook(name, version = '>= 0.0.0', options = {})
  cookbook name, version, { :path => "./cookbooks/#{name}" }.merge(options)
end

Then for all the "internal" cookbooks, in the ./cookbooks directory, I
have entries like this:

internal_cookbook "housepub-workstation"
internal_cookbook "users"

Internally at Opscode, we're currently doing something like this, too.
We're working to move to a single-repo-per-cookbook as a longer term
goal.

Hope this helps,
Joshua

[1]: 
http://jtimberman.housepub.org/blog/2012/11/19/chef-repository-berkshelf-conversion/
- apparently a year ago in fact :).

On Fri, Nov 29, 2013 at 3:47 AM, Kevin Yank 
<
 >
 wrote:
> On 29 Nov 2013, at 2:27 pm, Kevin Yank 
> <
 >
>  wrote:
>
>> Is this how others are using Berkshelf with a chef-repo, or have I missed 
>> something?
>
>
> Answering my own question, I finally stumbled on a GitHub Issue that 
> explains it all. If only the docs did as well!
>
> I’ve posted my own summary for the curious:
> https://github.com/berkshelf/berkshelf/issues/535#issuecomment-29508430
>
> --
> Kevin Yank
> Chief Technology Officer, Avalanche Technology Group
> http://avalanche.com.au/
>



-- 
Joshua Timberman, Opscode, Inc.