I’ve created a couple tickets for some pretty significant changes to
Opscode’s nginx cookbook.
First, COOK-19520. 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-19531. 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,
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
Joshua Timberman, Technical Community Manager
IRC, Skype, Twitter, Github: jtimberman