[chef] Re: Rebuild my chef !

[Ranjib Dey < >]

This is what i'd  do:
1) integrate berkshelf

2) Wont split t e cookbooks into separate repos

3) Move  the cookbook that's takes from community to a separate dir from org specific cookbooks

4)chances are high the community cookbooks are modified, identify them, port them to separate wrapper cookbooks or something else (and write chefspec tests against them)

5) Once step 4 is done get rid the community cookbook dir completely

6) Setup test-kitchen/minitest against the org specific staff

On Mon, May 6, 2013 at 9:38 AM, Jorge Espada < " target="_blank"> > wrote:

Ohai Chefs!

At my org we still have a monolithic chef-repo, with very little testing.. lets say the old way, being said that

I'm looking for advice/comments on how to rebuild this. Things that I think are no brainer:

- Have a chef server per environment: hosted chef for prod, ideally will be good to have for the others env too, but monay is the constrain here so OS for non prod env

- Use a git repo per cookbook

- use berkshelf

- test all the things (foodcritic, test-kitchen, chef-spec, mini-test)

Still I can't decide what to do with environment regarding cookbooks, have a branch per environment, like master(prod), test, dev or use

another method

Any other comments, ideas, recommendations are welcome

Thanks for being an awesome community :)

--

Jorge Espada