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

Fix up docs and pushed to gh-pages.

Browse Source
This commit is contained in:
Paul J. Davis 2010-05-06 14:05:22 -04:00
parent 08af4598cd
commit 4bf5d8e4bd
2 changed files with 25 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/htdocs/deployment.html
View File

@ -151,8 +151,22 @@ location / {
....
</pre>
</div>
<div class="section" id="working-with-virtualenv">
<h1>Working with Virtualenv</h1>
<p>To serve an app from a <a class="reference external" href="http://pypi.python.org/pypi/virtualenv">Virtualenv</a> it is generally easiest to just install
Gunicorn directly into the Virtualenv. This will create a set of Gunicorn
scripts for that Virtualenv which can be used to run applications normally.</p>
</div>
<div class="section" id="daemon-monitoring">
<h1>Daemon Monitoring</h1>
<div class="note">
<p class="first admonition-title">Note</p>
<p class="last">Make sure that when using either of these service monitors you do not
enable the Gunicorn's daemon mode. These monitors expect that the process
they launch will be the process they need to monior. Daemonizing
will fork-exec which creates an unmonitored process and generally just
confuses the monitor services.</p>
</div>
<p>A popular method for deploying Gunicorn is to have it monitored by <a class="reference external" href="http://smarden.org/runit/">runit</a>.
An <a class="reference external" href="http://github.com/benoitc/gunicorn/blob/master/examples/gunicorn_rc">example service</a> definition:</p>
<pre class="literal-block">

21
doc/site/deployment.rst
View File

@ -112,13 +112,21 @@ the proxy_redirect directive::
}
....
Working with Virtualenv
-----------------------
To serve an app from a Virtualenv_ it is generally easiest to just install
Gunicorn directly into the Virtualenv. This will create a set of Gunicorn
scripts for that Virtualenv which can be used to run applications normally.
Daemon Monitoring
-----------------
.. note::
Make sure that when using either of these service monitors make sure
that you do not enable the daemon mode. These monitors expect that the
process they launch will be the process they need to monior. Daemonizing
Make sure that when using either of these service monitors you do not
enable the Gunicorn's daemon mode. These monitors expect that the process
they launch will be the process they need to monior. Daemonizing
will fork-exec which creates an unmonitored process and generally just
confuses the monitor services.
@ -150,13 +158,6 @@ Another useful tool to monitor and control Gunicorn is Supervisor_. A
autorestart=true
redirect_stderr=True
Working with Virtualenv
-----------------------
To serve an app from a Virtualenv_ it is generally easiest to just install
Gunicorn directly into the Virtualenv. This will create a set of Gunicorn
scripts for that Virtualenv which can be used to run applications normally.
.. _Nginx: http://www.nginx.org
.. _slowloris: http://ha.ckers.org/slowloris/