You don’t need a git ‘server’, git work well without centralisation,
only on local machine.
That said, don’t use a single repo with all cookbooks and “knife
cookbook site install”, at a time (soon enough) you’ll end up with a lot
of branches (one per cookbook) and incompatibles states between branches
which will get knife cookbook site install unusable.
My advice would be to download the tar.gz from supermaket and extract it
in your repo, you’ll end up with something more usable.
Le 2014-10-29 14:16, Vikas Roonwal a écrit :
Thanks for the clarification Morgan.
Will get started with a local git server.
On Oct 29, 2014 6:05 PM, “Morgan Blackthorne” firstname.lastname@example.org wrote:
knife cookbook site install requires git. Chef does not. You can accomplish the same thing manually but you will not be able to get that knife command to work with SVN.
~~ StormeRider ~~
“Every world needs its heroes […] They inspire us to be better than we are. And they protect from the darkness that’s just around the corner.”
(from Smallville Season 6x1: “Zod”)
On why I hate the phrase “that’s so lame”… http://bit.ly/Ps3uSS 
On Wed, Oct 29, 2014 at 8:22 AM, email@example.com wrote:
I am new to Chef and have been able to install the Chef server on an RHEL
machine and chef-client version 11.16.4 on a windows machine.
When running the knife cookbook site install command on windows
I get an error stating that the folder e:/chef-repo/cookbooks is not a git
The setup steps for chef-repo state that it is not necessary to use git and one
can download the tar, extract it and then commit to the source control of
choice (SVN or CSV).
Is this correct? Is there a setting that needs to be changed to enable knife to
work with SVN instead of GIT?