- From: Miquel Torres <
>
- To:
- Subject: [chef] Re: Re: Re: About Opscode's cookbook repo changes
- Date: Tue, 21 Jun 2011 20:19:08 +0200
- Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=UxxLFVrh0qDza7bkQ23Jc5+TufEpR0/0rCFSBxJvFveUunUJW3Pwj9gxDRlYWSdawF RA7xD4QJ5Pgr6v95ygR+7stSpndPlONPG86lBrygHrNUjlWiT8KckRQxzBlngJznnaFq Pr7vVg6p2hcS9PeX93ULNf3Qszl8bPKvyqLtA=
I'd rather say, "via ssh" ;-)
2011/6/21 Grig Gheorghiu
<
>:
>
It's a Python-based package that allows you to build nodes
>
withchef-solo by pushing cookbooks to the nodes via Fabric.
>
>
https://github.com/tobami/littlechef
>
http://sysadvent.blogspot.com/2010/12/day-9-automated-deployments-with.html
>
>
On Tue, Jun 21, 2011 at 9:33 AM, Jeffrey E. Sussna
>
<
>
>
wrote:
>
> What is this LittleChef?
>
>
>
>
>
> On Jun 17, 2011, at 4:10 AM, Miquel Torres wrote:
>
>
>
>> Hi all,
>
>>
>
>> last month there was a post regarding changes in the opscode cookbooks
>
>> repo:
>
>> http://www.opscode.com/blog/2011/05/24/update-on-the-future-of-opscodes-cookbooks/
>
>>
>
>> While I can understand the reasons that made Opscode remove the
>
>> metadata.json from all cookbooks, it does pose a big problem for
>
>> non-ruby tools like LittleChef, which depended on JSON to
>
>> inter-operate.
>
>>
>
>> Is there a way to generate metadata.json for all cookbooks that
>
>> doesn't need a Chef Server?
>
>> "knife cookbook metadata" doesn't classify there, unfortunately.
>
>>
>
>> Cheers,
>
>> Miquel
>
>
>
>
>
- [chef] Re: About Opscode's cookbook repo changes, (continued)
Archive powered by MHonArc 2.6.16.