I’d like to clarify this for other users.
The “knife cookbook site” commands built into Chef and knife operate on the Opscode Chef Community Site through its API0 and are completely unrelated to GitHub or any other source repository.
Opscode recommends using the cookbooks from the community site at least for the cookbooks that we publish2, rather than the Git Repositories3. The ones on the site are tested and released artifacts. That isn’t necessarily the case with the “in development” Git repositories. This is similar to RubyGems, CPAN, or other packages/plugins.
Of course, you’re more than welcome to use the GitHub repositories directly if you’re willing to accept the risks inherent in using something that may be “in development”. The librarian-chef and berkshelf projects are both great at keeping track of all the repository based cookbooks you want to use.
Hope this helps.
On Oct 15, 2012, at 12:03 PM, email@example.com wrote:
I’m using knife to download cookbooks from the opscode git repo, using “knife
cookbook site download COOKBOOK”, and this works well.
I’m going to add another remote for my git repo so I can push changes to my
local repo. Does “knife cookbook download” depend on the opscode repo being the
origin? Or is there a way to configure the remote name?
Joshua Timberman, Technical Community Manager
IRC, Skype, Twitter, Github: jtimberman