Updates and Changes to Droplet - Gunicorn Command

Hello, I was wondering whether it is better after making changes such as uploading updated files to my droplet (Ubuntu Server) should I do which command for Gunicorn restart:

PID=$(systemctl show --value -p MainPID gunicorn.service) && kill -HUP $PID

or ~

sudo systemctl restart gunicorn

I’ve been using the second command with no issues, but am wondering whether it is better to get the process ID and kill it?

Submit an answer

This textbox defaults to using Markdown to format your answer.

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

Sign In or Sign Up to Answer

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,

It’s a lot better to restart gunicorn using systemctl restart gunicorn rather than using the kill command.

THe kill command shouldn’t be such a problem as it sends a signal to the app to shutdown itself but using systemctl is preferable.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.