[chef] Re: Nginx cookbook changes/improvements


Chronological Thread 
  • From: Andrea Campi < >
  • To: " " < >
  • Subject: [chef] Re: Nginx cookbook changes/improvements
  • Date: Sun, 25 Nov 2012 00:03:53 +0100




On Sat, Nov 24, 2012 at 11:51 PM, Joshua Timberman < " target="_blank"> > wrote:
Second, COOK-1953[1]. This proposes the removal of all the source
compiling parts of the nginx cookbook to a new cookbook, "nginx_source."
This will help narrow the scope of nginx as a library-esque cookbook that
provides common default components that can be used no matter if nginx is
installed via package or from source - recipes, definitions, attributes,
etc.

There's a number of benefits, least of all is that maintaining the "nginx"
cookbook will be easier, as will testing it with test-kitchen.

Does this change give anyone heartburn? In other words, is anyone
particularly strongly tied to having a single cookbook that handles the
relatively simple and straightforward package install vs the arduous and
complex source install that is required for basic nginx module
customization?


You have my +1
I've been working in this area for my upcoming CloudFoundry cookbooks, and reusing and customizing the nginx cookbookx is a PITA right now.
The change you suggest would make things easier to understand and hopefully to change, and that's very welcome.  



Archive powered by MHonArc 2.6.16.

§