Avoid silently falling back to a default nginx conf template

It is dangerous to use a somehow arbitrary template in case
of misconfiguration. Instead it should fail.
Merge pull request #3 from KingCrunch/no-template-fallback

Avoid silently falling back to a default nginx conf template
Bump to 2.0.0
Update readme with nginx_template changes
Update version reference in readme
fix(template) the static files wasn't being served from the correct folder
chore(version) Bump to 2.0.1
Fixed mixed up host and port in example config.
Added note on where settings should go.
Using capistrano 3.2.1 the old #{varname} syntax no longer worked, switched to using capistrano's fetch(...) in example file.
Merge pull request #7 from jjabba/clearifyfileforsettings

Added note on where settings should go.
Merge pull request #8 from jjabba/portandhostmixup

Fixed mixed up host and port in example config.
Static folder example setting incorrectly used :nginx_root_path
Merge pull request #10 from jjabba/staticexamplestaticfolder

Static folder example setting incorrectly used :nginx_root_path
Added switchable nginx service path for users who do not allow passwordless access to the full service scripts for their deployment user, but rather limits passwordless sudo access to the init.d/nginx script. Also had to refactor the nginx configuration test as well since it was running (/usr/sbin/)nginx directly.
Merge pull request #11 from jjabba/nginxbinchoice

Added switchable nginx service path
Swopped capistrano default methods into regular "#{method_name} type calls. Using fetch to retrieve variables previously set using set.
Merge branch 'master' of github.com:platanus/capistrano3-nginx into usingfetch
Merge pull request #9 from jjabba/usingfetch

Change to fetch when using some variables in the readme
fix(ssl): Fix the ssl variables and template