[chef] Re: Re: Workflows, librarian, cookbooks as individual git repositories, and other headaches

[Jason Boxman < >]

On Fri, Apr 20, 2012 at 3:52 PM, Jeremiah Snapp
<
 >
 wrote:
> I don't have a rake task to handle making sure all my cookbooks have been
> pushed.
>
> But I do have a way to manage my cookbooks that could solve the problem of
> making sure a colleague knows what's in the site-cookbooks directory.
> I really like Librarian for managing cookbooks but I use it a little
> different than it's documentation suggests.
>
> Among other things I don't include site-cookbooks in my knife cookbook_path.
>  Instead I put git hosted cookbooks outside my chef-repo and source them
> using :path in Cheffile while testing them.  I also keep a commented :git
> source to the cookbooks in Cheffile so once I push changes to github I
> comment the :path entries and uncomment the :git entries.
>
> I describe this more completely here.
>
> https://github.com/jeremiahsnapp/chef-repo/wiki/Chef-Cookbook-Management

That's a great workflow and I do something very similar myself.  Being
lazy, I abuse rb-inotify under Linux to monitor changes to my external
cookbooks directory so any file adds or deletions by me are hardlinked
inside my site-cookbooks directory, rather than forcing librarian to
update every time I update a file.  I then share out my chef repo via
VBox for testing.

-- 
Thursday next week is indeed time for a thorough insight
into the swirling red debian vortex. — leeta