- From: Ringo De Smet <
>
- To: Chef Users <
>, Chef Dev <
>
- Subject: [chef] Re: [[chef-dev]] Future of Opscode Cookbooks
- Date: Fri, 6 May 2011 09:05:24 +0200
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=muCKpeHwe19XNpcGemu90tFuy1owrx4Pm03McqE/bOkcaMxCXuhFXYsRoZbTKSnsMR k3LzEC+STdh7csPAEIS/sZn4B3KmOQb1BpE59cUYL9sf3WJHLEUe30BXXmMKVDjH5NBB NeW/Im6wJi3y85W+3RE3EoqcPGCzLTNzGjqsY=
Joshua,
On 5 May 2011 19:51, Joshua Timberman
<
>
wrote:
>
Additionally, we have two new cookbooks specifically related to the Chef
>
0.10 server installation:
>
>
* chef-server
Almost looks good:
https://github.com/opscode/cookbooks/blob/0.10.0/chef-server/metadata.rb
This one still points to rabbitmq_chef while in the recipes
themselves, the "rabbitmq::chef" recipe is already used/included. Once
this is fixed, can you publish both rabbitmq (including chef recipe)
and chef-server cookbooks again so I can "knife cookbook site install"
them into my repo? This is the only thing keeping me away from
bootstrapping a Chef server via the Chef Solo + chef-server cookbook
with Vagrant.
Ringo
Archive powered by MHonArc 2.6.16.