diff --git a/doc/htdocs/deployment.html b/doc/htdocs/deployment.html index 6a3a5305..34cf3ce0 100644 --- a/doc/htdocs/deployment.html +++ b/doc/htdocs/deployment.html @@ -135,8 +135,8 @@ http { features like Comet, Long polling, or Web sockets, you need to turn off the proxy buffering. When you do this you must run with one of the async worker classes.

-

To turn off buffering, you only need to add proxy_buffering off; to your -location block:

+

To turn off buffering, you only need to add proxy_buffering off; to your +location block:

 ...
 location / {
@@ -168,7 +168,7 @@ $ ~/venvs/webapp/bin/easy_install -U gunicorn
 $ deactivate

Then you just need to use one of the three Gunicorn scripts that was installed -into ~/venvs/webapp/bin.

+into ~/venvs/webapp/bin.

Daemon Monitoring

diff --git a/doc/htdocs/faq.html b/doc/htdocs/faq.html index 6c8a0613..bc38c22e 100644 --- a/doc/htdocs/faq.html +++ b/doc/htdocs/faq.html @@ -55,12 +55,12 @@ deployment page. Test some more.
What types of workers are there?

These can all be used with the -k option and specifying them -as egg:gunicorn#$(NAME) where $(NAME) is chosen from this list.

+as egg:gunicorn#$(NAME) where $(NAME) is chosen from this list.

How might I test a proxy configuration?
@@ -87,8 +87,8 @@ $ kill -TTOU $masterpid
Start gunicorn with an approximate number of worker processes. Then use the TTIN and/or TTOU signals to adjust the number of workers under load.
How do I set SCRIPT_NAME?
-
By default SCRIPT_NAME is an empy string. The value could be set by -setting SCRIPT_NAME in the environment or as an HTTP header.
+
By default SCRIPT_NAME is an empy string. The value could be set by +setting SCRIPT_NAME in the environment or as an HTTP header.
How can I name processes?
You need to install the Python package setproctitle. Then you can specify a base process name on the command line (-n) or in the configuration diff --git a/doc/htdocs/installation.html b/doc/htdocs/installation.html index e6313d33..9cc3033c 100644 --- a/doc/htdocs/installation.html +++ b/doc/htdocs/installation.html @@ -59,8 +59,8 @@

Installing with easy_install

-

If you don't already have easy_install available you'll want to download -and run the ez_setup.py script:

+

If you don't already have easy_install available you'll want to download +and run the ez_setup.py script:

 $ curl -O http://peak.telecommunity.com/dist/ez_setup.py
 $ sudo python ez_setup.py -U setuptools
@@ -89,7 +89,7 @@ $ git clone git://github.com/benoitc/gunicorn.git
 $ python setup.py install

If you've cloned the git repository, its highly recommended that you use the -develop command which will allow you to use Gunicorn from the source +develop command which will allow you to use Gunicorn from the source directory. This will allow you to keep up to date with development on GitHub as well as make changes to the source:

@@ -111,20 +111,20 @@ $ easy_install -U gevent    # For gevent workers

Note

-

If installing greenlet fails you probably need to install +

If installing greenlet fails you probably need to install the Python headers. These headers are available in most package managers. On Ubuntu the package name for apt-get is python-dev.

-

Gevent also requires that libevent 1.4.x or 2.0.4 is installed. +

Gevent also requires that libevent 1.4.x or 2.0.4 is installed. This could be a more recent version than what is available in your -package manager. If Gevent fails to build even with libevent +package manager. If Gevent fails to build even with libevent installed, this is the most likely reason.

Installing on Ubuntu/Debian systems

If you use Ubuntu karmic, you can update your system with packages from -our PPA by adding ppa:bchesneau/gunicorn to your system's Software +our PPA by adding ppa:bchesneau/gunicorn to your system's Software Sources.

Or this PPA can be added to your system manually by copying the lines below and adding them to your system's software sources: