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.
This commit is contained in:
parent
b65fccd416
commit
f4af965a2e
1 changed files with 2 additions and 2 deletions
4
setup.md
4
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/<forum.hostname.com> /etc/nginx/sites-enabled/<forum.hostname.com>
|
||||
```
|
||||
|
||||
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.
|
||||
via your hostname, assuming that it points to your VPS' IP address.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue