I have Django running under Gunicorn under NginX on a digital ocean installation that I had set up out of the box. After upgrading Django to 1.7, I wanted to do a quick test that I hadn't broken anything.
So I tweaked the settings and found that nothing had changed. Restarted nginX and nothing changed. Finally I went to Gunicorn.
As mentioned here, you "gracefully reload" using the command
$ kill -HUP masterpid
But that means you have to find out what masterpid is.
Here's one way to find out, given here:
$ pstree -ap|grep gunicorn
look for the number on the top toward the left.
No comments:
Post a Comment