Question
Updates and Changes to Droplet - Gunicorn Command
- Posted on April 19, 2022
- DigitalOcean DropletsUbuntu 20.04
Asked by mpasquali
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?
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!
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.
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.
Hi @mpasquali,
It’s a lot better to restart gunicorn using
systemctl restart gunicornrather 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.