[chef] Re: Re: App cookbooks

[David Morton < >]

In our case, I have to disagree, since most of our devs don't want to deal with devops.  We have a lot of apps, but not very much server complexity for any one app.  We have a git hook based deploy process, so if a single cookbook can provision servers based on a data structure in data bags,  I think I can limit the ops side to those who deal with server provisioning, and have the server set up ready to accept a git push to deploy the app.   Having all the servers provisioned with chef, though, will help standardize all the environments.  Eventually, the cookbooks will need very little maintenance, and I won't have to create a new cookbook every time we start a new app - just add some data values and bootstrap the new servers.

Later I may add a rails app to manage the data bag data, allowing for quick provisioning of new app servers.

On 1/2/14 5:13 PM, JJ Asghar wrote:

" type="cite">

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: "> | c: 512.619.0722 | o: 512.977.5876

From: "Mark H. Nichols" < "> >
Reply-To: < "> >
Date: Thursday, January 2, 2014 at 3:33 PM
To: < "> >
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 

-- 
David Morton

 
 ">