[chef] Re: Re: Re: Re: Installing handlers with chef_handler

[Zac Stevens < >]

Hi Seth,

On Thu, Jul 21, 2011 at 5:26 PM, Seth Chisamore 
<
 >
 wrote:
> You could fork the repo, but the preferred way would be to just track the 
> upstream cookbook in your local chef-repo using the 'vendor branch' 
> pattern. An implementation of this pattern (that works with git) is built 
> into 'knife cookbook site install'.
>
> This command does the following:
<--snip-->

Yup, I know all that - but it's not much good for being able to show
this list what I've done with the cookbook that I'm having trouble
with :)

Other possible alternatives are pasting stuff into the message,
attaching files, or dumping stuff into gists - but all of those feel a
bit crufty.

In other words, there's a well-documented workflow for managing one's
own repository, when everything's going well.  However, that workflow
doesn't seem well-suited either to soliciting help, or pushing
fixes/improvements upstream.  It's those angles I'm struggling with.

Cheers,


Zac