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 a few typos and improved clarity for systemd docs (#1398)

Browse Source
This commit is contained in:
David McInnis 2016-11-22 14:40:02 -08:00 committed by Berker Peksag
parent a713fa9a65
commit ea741854ec
1 changed files with 9 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
docs/source/deploy.rst
View File

@ -212,7 +212,7 @@ A tool that is starting to be common on linux systems is Systemd_. Below are
configurations files and instructions for using systemd to create a unix socket configurations files and instructions for using systemd to create a unix socket
for incoming Gunicorn requests. Systemd will listen on this socket and start for incoming Gunicorn requests. Systemd will listen on this socket and start
gunicorn automatically in response to traffic. Later in this section are gunicorn automatically in response to traffic. Later in this section are
nstructions for configuring Nginx to forward web traffic to the newly created instructions for configuring Nginx to forward web traffic to the newly created
unix socket: unix socket:
**/etc/systemd/system/gunicorn.service**:: **/etc/systemd/system/gunicorn.service**::
@ -227,7 +227,7 @@ unix socket:
User=someuser User=someuser
Group=someuser Group=someuser
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/socket 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
@ -251,27 +251,22 @@ unix socket:
d /run/gunicorn 0755 someuser somegroup - d /run/gunicorn 0755 someuser somegroup -
Next enable the services so they autostart at boot:: Next enable the socket so it autostarts at boot::
systemctl enable gunicorn.service
systemctl enable gunicorn.socket systemctl enable gunicorn.socket
Either reboot, or start the services manually:: Either reboot, or start the services manually::
systemctl start gunicorn.service
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/socket http``, Gunicorn
should start and you should see something like that in logs:: should start and you should see some HTML from your server in the terminal.
2013-02-19 23:48:19 [31436] [DEBUG] Socket activation sockets: You must now configure your web proxy to send traffic to the new Gunicorn
unix:/run/gunicorn/socket,http://0.0.0.0:9000,http://[::]:8000 socket. Configure your ``nginx.conf`` like the following:
If you are also using Nginx with Systemd make sure to pass incoming traffic to **/etc/nginx/nginx.conf**::
the new Gunicorn socket. Below is the http section of my nginx.conf
**/etc/tmpfiles.d/gunicorn.conf**::
http { http {
include mime.types; include mime.types;
default_type application/octet-stream; default_type application/octet-stream;
@ -311,7 +306,7 @@ Now you should be able to test Nginx with Gunicorn by visiting
http://127.0.0.1:8000/ in any web browser. Please note that the listen and http://127.0.0.1:8000/ in any web browser. Please note that the listen and
server_name used here are configured for a local machine. In a production server_name used here are configured for a local machine. In a production
server you will most likely listen on port 80, and use your URL as the server you will most likely listen on port 80, and use your URL as the
server_name. Apache or any other web-server can be used instead of Nginx. server_name.
Logging Logging