jingrow/gunicorn
1
0
Fork 0
mirror of https://github.com/frappe/gunicorn.git synced 2026-01-14 11:09:11 +08:00
Code Issues Packages Projects Releases Wiki Activity

Fixed systemd documentation to properly setup gunicorn unix socket

Browse Source 
The systemd files recommended in the docs do not work. The socket file disappears after the first request, or after the service is restarted. 

This commit updates the systemd files to include the correct settings
This commit is contained in:
Arianit Uka 2018-10-12 14:46:08 -04:00 committed by Randall Leeds
parent 80dfe06943
commit bb0b366b26
1 changed files with 7 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/source/deploy.rst
View File

@ -233,7 +233,7 @@ unix socket:
RuntimeDirectory=gunicorn RuntimeDirectory=gunicorn
WorkingDirectory=/home/someuser/applicationroot WorkingDirectory=/home/someuser/applicationroot
ExecStart=/usr/bin/gunicorn --pid /run/gunicorn/pid \ ExecStart=/usr/bin/gunicorn --pid /run/gunicorn/pid \
--bind unix:/run/gunicorn/socket applicationname.wsgi --bind unix:/run/gunicorn.sock applicationname.wsgi
ExecReload=/bin/kill -s HUP $MAINPID ExecReload=/bin/kill -s HUP $MAINPID
ExecStop=/bin/kill -s TERM $MAINPID ExecStop=/bin/kill -s TERM $MAINPID
PrivateTmp=true PrivateTmp=true
@ -247,8 +247,10 @@ unix socket:
Description=gunicorn socket Description=gunicorn socket
[Socket] [Socket]
ListenStream=/run/gunicorn/socket ListenStream=/run/gunicorn.sock
User=someuser
Group=someuser
[Install] [Install]
WantedBy=sockets.target WantedBy=sockets.target
@ -265,7 +267,7 @@ Either reboot, or start the services manually::
systemctl start gunicorn.socket systemctl start gunicorn.socket
After running ``curl --unix-socket /run/gunicorn/socket http``, Gunicorn After running ``curl --unix-socket /run/gunicorn.sock http``, Gunicorn
should start and you should see some HTML from your server in the terminal. should start and you should see some HTML from your server in the terminal.
You must now configure your web proxy to send traffic to the new Gunicorn You must now configure your web proxy to send traffic to the new Gunicorn
@ -279,7 +281,7 @@ socket. Edit your ``nginx.conf`` to include the following:
listen 8000; listen 8000;
server_name 127.0.0.1; server_name 127.0.0.1;
location / { location / {
proxy_pass http://unix:/run/gunicorn/socket; proxy_pass http://unix:/run/gunicorn.sock;
} }
} }
} }