[chef] Re: RE: Re: App cookbooks

[Dylan Northrup < >]

Personally, the rule of thumb I have is use a shared cookbook until complexity of applications diverges to the point it "makes sense" to split the cookbook into multiple different ones. It's largely a matter of taste, but I've been bitten too many times by code fixes not being deployed everywhere.  By having multiple apps use the same cookbook, I use change inertia in my favor to stave off the cookbook split until it's absolutely necessary (and, in the process, helping insure fixes made to a cookbook affect as many apps/services/sites as possible).  Works for me, but YMMV.

On Fri, Jan 3, 2014 at 12:31 AM, Kadel-Garcia, Nico < " target="_blank"> > wrote:

One cookbook per app means modularity. Changes in one small, well built application do not impinge on the other applications, and enhancements to the logic or attributes are not so reliant on avoiding conflict with interwoven applications.

---

From: JJ Asghar < " target="_blank"> >
Sent: Thursday, January 02, 2014 6:13 PM
To: " target="_blank">
Subject: [chef] Re: App cookbooks

 

I like the idea of one cookbook per app.

It allows for expandability and scaling opportunity.  

If that makes sense :)

Best Regards,

JJ Asghar

e: " target="_blank"> | c: 512.619.0722 | o: 512.977.5876

From: "Mark H. Nichols" < " target="_blank"> >
Reply-To: < " target="_blank"> >
Date: Thursday, January 2, 2014 at 3:33 PM
To: < " target="_blank"> >
Subject: [chef] App cookbooks

All -

What’s the community consensus on cookbooks to deploy applications. One per app? Or a generalized cookbook that can deploy any app (as long as it follows a set pattern)?

Thanks,

Mark

--

mark nichols | (t|a.n) @zanshin | (w) zanshin.net