Reboot or Restart Nginx?

When I run my dev server offline for Django, I can just restart the Django server after I make changes to test. I then upload changed files to Digital Ocean. I’m finding out I need to restart my server on the droplet for changes to take full effect for my Django apps. Should I just restart Nginx instead? I’m also running Gunicorn. Or should I activate my virtual environment and restart the Django server?


By the way, I’m currently staging, so restarting is not a major factor. However, I would like to know the best way to have changes to my files take effect. Once I am not in staging environment, I will not be able to reboot unless I am down for maintenance.

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Accepted Answer

Hi @mpasquali,

Yes, when you make changes to config and familiar files you need to restart the service you are making these changes on. For instance, if you are updating the Nginx config for your Domain then most certainly afterwards you need to restart Nginx.

There is no need to reboot the whole droplet, just a simple restart/reload should be enough.