Mads Skjern's questions

I keep forgetting to reload nginx settings, sudo service nginx reload, while working on / experimenting / learning the config files, nginx (and other included config files).

Is there a way of achieving this, that nginx reloads configuration files, after any of the changes below:

• /etc/nginx/nginx.conf
• /etc/nginx/sites-available/ (any changes, deletion, creation of files)
• /etc/nginx/sites-enabled/ (any changes, deletion, creation of files)

You may think it's just silly/stupid that I forget to reload, but while being new and actually learning and experimenting, there is really enough to keep track of.

While the uwsgi documentation is perhaps fine for someone already familiar with server administration, it is definitely not so helpful for someone trying to learn it. I hope someone can help out with the questions below.

1. I read, that it can close/reload processes gracefully. But what does that mean? And what is the alternative to closing gracefully?

2. When is it that these processes can close gracefully/ugly? Is it if a process crash? Or if I chose to close uwsgi, eg by pressing ctrl+c? Or in some other case? Can I test out this gracefulness, eg provoke smth to crash / close, and then see the result with and without master?

3. Does it do anything else than letting processes close gracefully?

4. Since the enabling the master process is optional, there must be cases where it is not beneficial to use it. What are these cases?