{"componentChunkName":"component---src-templates-post-template-js","path":"/nginx-per-site-conf","webpackCompilationHash":"9f9b08718447f3d4e396","result":{"data":{"markdownRemark":{"id":"b7f49102-068d-5ad9-8aae-153d34714813","html":"

Somehow I wasn’t able to find this old mechanic in the documentations and within the first page of google results while looking for it for a memory refresh, so here we go with a rustic explanation, mostly for myself

\n

There is a modular way to write nginx.conf blocks (http location config blocks for example), in a per-site fashion (similar approach as using ‘a2ensite’ and ‘a2dissite’ in apache)

\n

This is helpful to keep an easy to maintain conf file when you have multiple sites/domains/subdomains configurations in the same server.

\n

Quick how to

\n

Change the site config at /sites-available/ and then make sure that the symlink to that file exists at /sites-enabled/, if it doesn’t create it with ln -s, example:

\n
ln -s /etc/nginx/sites-available/mysite-production /etc/nginx/sites-enabled/
\n

Then restart nginx

\n

How it works

\n

Nginx consists of modules which are controlled by directives specified in the configuration file that you can usually find at /etc/nginx/nginx.conf\\

\n

A way to load the per-site configuration is having this at the bottom in that file:

\n
location @mysite_production {\n  include /etc/nginx/conf.d/*.conf;\n  include /etc/nginx/sites-enabled/*;\n}
\n

so it will include the configuration from the files found in that folder there, which are actually symlinks to the ones at /sites-available folder, more about that next.

\n

How to update them

\n

The way that you can opt-in which one to include in the live configuration is adding or removing symlinks from /sites-available/ to /sites-enabled/

\n

If you update the config file located at /sites-available/mysite-production it will be included in the main nginx configuration only if the symlink exists in the /sites-enabled/ folder. Changes will be reflected at sites-enabled since the symlink just links to the original file from sites-available

\n

That way you can serve multiple configurations, and enable/disable them to quickly test stuff or to scope per-site or even per-environment configurations.

\n

To create a symlink you can write something like this:

\n
ln -s /etc/nginx/sites-available/mysite-production /etc/nginx/sites-enabled/
\n

And to remove it just go with the old rm or unlink command, pointing to the symlink path.

\n

After that make sure to restart nginx to pick up the config changes sudo service nginx restart

","fields":{"slug":"nginx-per-site-conf","tagSlugs":["/tag/nginx/","/tag/per-site/","/tag/configuration/","/tag/sites-available/","/tag/sites-enabled/"]},"frontmatter":{"date":"2020-05-04T14:48:44.854Z","description":"A quick reminder on how sites-available and sites-enabled configurations work on Nginx and how to properly update them.","tags":["nginx","per-site","configuration","sites-available","sites-enabled"],"title":"Nginx per-site configuration","socialImage":null}}},"pageContext":{"isCreatedByStatefulCreatePages":false,"slug":"nginx-per-site-conf"}}}