[chef] Re: Re: Workflow of Making, Testing and Using a Cookbook?

[Matt Stratton < >]

Julian,

Not to go off on a tangent, but I'm curious about a statement in here. You mention that the cookbook should not be "using git submodules or any of that funny business".

What would be the negative reason for putting chef-repo in source control, and then all cookbooks in their own repos, but putting a submodule of each cookbook under the cookbooks directory of the chef-repo? I've been working on a few projects where we intended to do this eventually, and just haven't done so yet. What issues/problems might I not be realizing? :)

On Mon, May 19, 2014 at 9:49 AM, Julian C. Dunn < " target="_blank"> > wrote:

On Sun, May 18, 2014 at 11:08 AM, Kevin Meredith
< "> > wrote:
> I'm writing a cookbook that deploys a web app. The cookbook, "my_cookbook,"
> does the following:
>
> (1) install Java and Tomcat
> (2) copies a remote WAR into Tomcat's webapps directory.
>
> I'm using test-kitchen to test out this cookbook.
>
> Once this cookbook is properly tested, here's my understanding as to how to
> deploy it using chef-client & chef-server:
>
> (1) set up Chef Server to host "my_cookbook"
> --> involves forking opscode/chef-repo

Actually it doesn't involve that at all, though it's a good idea to
store your cookbook in source control (in its OWN repository, not as a
subdirectory of a 'chef-repo' repository or using git submodules or
any of that funny business). However, 'knife' doesn't care about that;
you merely need to upload your cookbook to the server.

> (2) install and set up chef-client on my "node", i.e. machine to be
> provisioned from Chef-Server

Right.

- Julian

--
[ Julian C. Dunn < "> >          * Sorry, I'm    ]
[ WWW: http://www.aquezada.com/staff/julian    * only Web 1.0  ]
[ gopher://sdf.org/1/users/keymaker/           * compliant!    ]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9       ]