Second, COOK-1953[1]. This proposes the removal of all the source[1]: http://tickets.opscode.com/browse/COOK-1953
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.
I am against making a nginix_source cookbook when a nginix::source recipe should be sufficient.
In terms of the "library cookbook" theres no reason you can't use nginix::library recipe with no content. Then people can load that up and do whatever they want.
Bigger discussion wrt library/app cooks, but IMO these goals can be obtained in the same recipe.
--
Opscode, Inc
Joshua Timberman, Technical Community Manager
IRC, Skype, Twitter, Github: jtimberman
Archive powered by MHonArc 2.6.16.