- From: Joshua Timberman <
>
- To: Chef Users <
>
- Subject: [chef] Nginx cookbook changes/improvements
- Date: Sat, 24 Nov 2012 22:51:30 +0000
- Accept-language: en-US
Ohai Chefs,
I've created a couple tickets for some pretty significant changes to
Opscode's nginx cookbook.
First, COOK-1952[0]. It seems that the bulk of the GeoIP recipe here has
nothing to actually do with nginx, and it should be moved to its own
cookbook, e.g. "geoip." The nginx-specific bits would be refactored into
the cookbook accordingly.
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?
[0]:
http://tickets.opscode.com/browse/COOK-1952
[1]:
http://tickets.opscode.com/browse/COOK-1953
--
Opscode, Inc
Joshua Timberman, Technical Community Manager
IRC, Skype, Twitter, Github: jtimberman
- [chef] Nginx cookbook changes/improvements, Joshua Timberman, 11/24/2012
Archive powered by MHonArc 2.6.16.