Add sites-enabled folder usage

[hasanalihaolader]

• Added sites-enabled folder due to availability for virtual host configuration
• Moved default configuration conf.d to site-enabled cause all enabled site virtual hosts in the server could be available in the site-enabled folder and conf.d folder available to another custom nginx configuration.

[LeoColomb]

Thanks for this pull request @hasanalihaolader.
That said I'm not sure to get the point of the change.
Virtual hosts can be easily configured in the conf.d folder, which is the standard one for Nginx.
Also, the current status of the default vhost is being disabled, and this is on purpose.

Thus, could you clarify?

[hasanalihaolader]

Thanks for this pull request @hasanalihaolader. That said I'm not sure to get the point of the change. Virtual hosts can be easily configured in the conf.d folder, which is the standard one for Nginx. Also, the current status of the default vhost is being disabled, and this is on purpose.

Thus, could you clarify?

@LeoColomb Nginx default configuration has the site-enabled folder, and it is possible to v-host configure in site-enabled. Just adopt this configuration, so at this moment, it is possible to v-host configuration in conf.d and site-enabled both.

site-enabled folder ensures v-host configuration for which site is enabled in this server.
another point is that the default configuration is not disabled. You see, the default configuration is in a site-enabled folder, so the default site is enabled for this server.

my purposes are clearly visible, such as which site is enabled on the server and the nginx default configuration structure adoption.
and minimize nested v-host configuration like if multiple site configuration in one .cnf is not clearly visible where this site configuration has.

[muuvmuuv]

Back in Apache days, I have seen this as well, but NGINX if far better to configure. You can simply append an .off to the host name to turn it “off” and include it using a proper regex. I don't see the need here to use an old pattern. And I had never the use of turning hosts off, since these configurations are mostly “set it and forget it”.

[hasanalihaolader]

Back in Apache days, I have seen this as well, but NGINX if far better to configure. You can simply append an .off to the host name to turn it “off” and include it using a proper regex. I don't see the need here to use an old pattern. And I had never the use of turning hosts off, since these configurations are mostly “set it and forget it”.

is not old configuration, is default configuration during install fresh nginx.

[LeoColomb]

Do you have any official documentation that illustrates the sites-enabled as a standard Nginx pattern?

I'm also quite skeptical, to be honest. That's why I'm closing this pull request.
But I'd be happy to reopen if any material is provided to support this change.
Meanwhile, you are of course free to use the pattern of your preference on your deployments.