- From: Nico Kadel-Garcia <
>
- To: "
" <
>
- Subject: [chef] RE: Re: Any reason not to use chefdk on chef-solo instances in order to get Berkshelf support?
- Date: Mon, 29 Dec 2014 13:02:37 -0600
- Accept-language: en-US
- Acceptlanguage: en-US
Librarian-chef is problematic. Updating a single cookbook tends to update all that cookbook’s “requirements” as well. Since this can get you into dependency hell very, very quickly, I can’t consider it safe or suitable for production use. Nico Kadel-Garcia Lead DevOps Engineer
">
From: Ranjib Dey [mailto:
Sent: Monday, December 29, 2014 1:55 PM
To:
Subject: [chef] Re: Any reason not to use chefdk on chef-solo instances in order to get Berkshelf support? if you need berkshelf then yes. alternatively. librarian-chef will not take a lot of time to install. On Mon, Dec 29, 2014 at 10:34 AM, Nico Kadel-Garcia <
" target="_blank">
> wrote: I’m noting that Berkshelf, in particular, is awkward to compile into pure chef client or chef-server deployments. Is there any reason not to simply install and use ‘chefdk’ for chef-solo clients, and avoid the lengthy compilation involved otherwise? Nico Kadel-Garcia Lead DevOps Engineer
" target="_blank">
|
Archive powered by MHonArc 2.6.16.