[chef] Re: Re: Anybody uses git subtree in a chef repo to development cookbooks separately from the production chef-repo ?

[Vladimir Skubriev < >]

29.10.2013 14:57, Eduardo Dias пишет:

" type="cite">

Hi Vladimir,

we use Git to manage our repo cookbooks.

We have 2 types of cookbooks, one that we call "base cookbooks", that we use for common installations, like Java, Tomcat, HAProxy, etc..(we do not change the community cookbooks, we use then as is and we extend if we need to change something). For these type of cookbooks, we use a repo in Git with the same name of cookbook, and the upload is directly. For the other type, that we call "project cookbooks", we use a directory inside of project repo, in our case, a directory named /project/build/cookbook (the build directory has others stuffs related to our Jenkins build system). To upload the cookbook we have a script in Ruby (you can use any script that you prefer) that copy the build cookbook directory to a temporary directory with the cookbook name and then, we execute the knife upload command.

It is a simple (not the best solution) but works.

Now I also use this strategy, but I manually controls my knife cookbook upload command. Doing cookbook updates in server in manual mode.

But also heard about chef-repo and therefore I have a question.

Because I would to store all my work in one place. But can't understand how to do it. )

The general idea of chef-repo. How I can understand is "Store all in chef-repo, and upload all to chef-server at all and in one knife command"

" type="cite">

I hope to had helped.

That's help os course. In "How this do others".

" type="cite">

Sorry also, for my bad English.

NO problem ) Of course )

" type="cite">

Regards

Eduardo. 

--

Atenciosamente,

Eduardo

-- 
Best regards,

CVision Lab System Administrator
Vladmir Skubriev