Add path to self signed certificate for ssl.no-default server block.

[bogdanhruban]

Based on some issues with multiple hosts (HTTPS) on a single nginx server, I had to add (self signed in my case) certificates for the ssl.no-default server block.

[AD7six]

Hey, thanks for the PR

I don't quite understand the use case, can you explain please? It's implicit that if you want to use ssl.no-default you're already using ssl for another server block, in which case you'd already have an ssl cert and can use that if necessary. The changes here also puts a hardcoded path in the template, which is something to avoid.

Creating a self-signed certificate, to allow listening on 443, just to return a 444 response - instead of just not listening on ssl at all is an effort for no gain from my perspective.

I would recommend to put the default certificate directives in the http block - if there's an issue that'll explain why I haven't seen it.

[LeoColomb]

With #204 merged, you can now easily configure default/custom certificates while keeping ssl configuration.