In complete nginx cookbook it says
"The /etc/nginx/conf.d/ directory contains the default HTTP server configuration file. Files in this directory ending in .conf are included in the top-level http block from within the /etc/ nginx/nginx.conf file. It’s best practice to utilize include state‐ ments and organize your configuration in this way to keep your configuration files concise. In some package repositories, this folder is named sites-enabled, and configuration files are linked from a folder named site-available; this convention is deprecated."
But why is that convention deprecated? I always felt it was easier to maintain multiple sites by just removing/adding the symlink between sites-available and sites-enabled, thus giving me control over which sites to serve without deleting configurations which I might again need in future.
If I use the new structure where all configs for all sites come from same conf.d folder, I'll have to rename file to not have conf extension or remove that conf file completely in order to temporary keep site unavailable.
Is there any new and better pattern/convention that I'm missing?