> As my changes will compile an |nginx.conf| file which includes
> |[...]/conf.d/*conf| and |[...]/sites-enabled/*| only, removing
> |[...]/sites-enabled/default| should be sufficient.
> 
> Also, as far as I have been using and have seen others use
> xyz-{available,enabled} directories:
> 
> 1) Store all possible configurations in xyz-available and
> 2) enable only the ones you need via syz-enabled.
> 
> e.g. if you run apache's a2dissite or a2dismod, only the {sites,mods}-enabled
> symlink is removed but not the whole configuration. The same applies to (newer)
> php, lighttpd, ... configuration (on Debian/Ubuntu).
> 
> What are your thoughts on this?

My concern is that the way you propose will give the module different behaviour
depending on the underlaying OS: on Debian and derivatives it would only disable
the vhost without removing it, while on RH and derivatives it will be
effectively removing all traces of the default vhost.

The idea suggested by the variable is that we *purge* the "default" config file,
so I expect, by it's name, to remove it completely from nginx's config dir.

Just disabling it should be achieved with
```puppet
nginx::vhost { 'default': ensure => disabled }
```
as with any other vhost management.


Perhaps adding another variable `$config_file_default_disable` would be a
possibility, but it would mean to also keep the file on RH's related (and
renaming it), and it's possible to achieve the same result in a cleaner way as
stated before.

I prefer the current behaviour for this variable (removing both files), for the
sake of coherence across OSes.

Al other changes from this PR are OK with me.