Default Site Config

Issue: If the default site is disabled via node attributes (which it is by default IIRC), then the default site config still gets written to disk and a reload command is sent to the nginx service.

This causes issues in our infrastructure because we have our own cookbook that writes out the default config and reloads nginx on its own. This issue (rendering and reloading the config twice) would have caused the main site to become unavailable in the time between reloads because an incorrect config is in place.

This patch makes it so that config is never written if the default site is disabled via node attributes.