Now I decide to choiche best method for creating and maintain a chef-repo.
When I started working with a chef I didn't using a chef-repo and starts development of my cookbooks in same directory in home.
For example: ~/chef-cookbooks
And there are my own cookbooks and community cookbooks.
Which is loading to the server via knife cookbook upload foldername.
My own cookbooks development with mercurial cvs.
Site cookbooks git cloned or unpacked from tar.gz and has not modified.
Now I have come to the conclusion that I needed a chef-repo to store all my data in one place.
How I can store community cookbooks and my own cookbooks in chef-repo (In which folders they should be) ?
I can convert my mercurial repositories with a cookbooks to git repos and include them in the chef repo.
What do you think about this ?
Can I revice more flexibiliy and usabilty instead of many problems in this use case ?
And how to include community git clonned cookbooks in my future chef-repo(I want to use a berkshelf) ? Using a git sub trees or something else?
In general, I want to get a fully managed and flex system.
Anybody uses git subtree in a chef repo to development cookbooks separately from the production chef-repo ?
Excusme for bad english.
--
Best regards,
CVision Lab System Administrator
Vladmir Skubriev
Archive powered by MHonArc 2.6.16.