add upstart support to nginx::source
recipe inserts daemon off into main conf, remove it from upstart.conf
add another attribute to accurately control upstart fore/background behavior
fix minor formatting issue in upstart template
Merge remote-tracking branch 'upstream/master' into COOK-2622
remove recipe defaults (use attribute defaults), fix README snafu, convert unless/nil to if
whitespace pedantry
Add configtest in initscript for CentOS.
Create director for the nginx pid file.
Moved node[nginx][passenger] attributes to nginx/attributes/passenger.rb
Merge pull request #99 from brandonmartin/COOK-2622

COOK-2622 - nginx: add upstart support
Merge pull request #104 from hnakamur/configtest_in_initscript

Add configtest in initscript for CentOS.
[COOK-2409] move service declaration to end of recipe

Previously the new runit_service resource would try to restart before 
the nginx code is compiled and available. This has the nasty side effect 
of causing the Chef run to fail!
Merge pull request #108 from opscode-cookbooks/COOK-2409

[COOK-2409] move service declaration to end of recipe
Move the directory definition of the pid file to nginx::commons_dir.
[COOK-2877] - remove test cookbook

Testing specific configurations will be handled by "suites".

Hopefully w/ COOK-2783, we won't need all the module specific tests anyway.
[COOK-2877] - update test kitchen support for 1.0

* Remove Gemfile (not needed as test-kitchen uses vagrant 1.1+)
* Convert Kitchenfile to .kitchen.yml, testing essential recipes only
  at this time
* Update ignores
* Add berksfile
[COOK-2877] - depend on the runit cookbook

Runit is the default init style for debian/ubuntu systems, so we need
to specify a dependency on it, otherwise, e.g., chef-solo won't load
the resources/providers and the runit_service will fail in the source
recipe. While one could use the init init_style attribute value, this
doesn't "just work" for most users.
Merge branch 'COOK-2877'
Add TESTING documentation