From f4af965a2e0c146c8d5e33e203cde3dd1c5e22b0 Mon Sep 17 00:00:00 2001 From: lallulli Date: Thu, 31 Oct 2019 11:36:05 +0100 Subject: [PATCH] Better way of updating nginx configuration Using `nginx -s reload` is better than restarting the server on live systems, because if there is any problem with new config files, nginx will warn you, refuse to reload and continue to work with old configuration. Moreover, this command will minimize downtime. --- setup.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/setup.md b/setup.md index ea3dc1b..d0f2d3e 100644 --- a/setup.md +++ b/setup.md @@ -100,7 +100,7 @@ You should then create a symlink to this file inside ``/etc/nginx/sites-enabled/ ln -s /etc/nginx/sites-available/ /etc/nginx/sites-enabled/ ``` -Then restart nginx by running ``sudo systemctl restart nginx``. +Then reload nginx configuration by running ``sudo nginx -s reload``. ### Supervisor @@ -168,4 +168,4 @@ You should see something like this: ## Conclusion That should be all you need to get started. Your forum should now be accessible -via your hostname, assuming that it points to your VPS' IP address. \ No newline at end of file +via your hostname, assuming that it points to your VPS' IP address.