summaryrefslogtreecommitdiff
path: root/docs/narr/project.rst
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2012-01-02 20:41:44 -0500
committerChris McDonough <chrism@plope.com>2012-01-02 20:41:44 -0500
commit030d10697cc52a5c26d19818140616a485f63428 (patch)
tree24a57f792ace5f1349b090d9ad4ee3657bd0539f /docs/narr/project.rst
parent2d7d36c7c3d7bd03f18d0cbec411da6bac2b05e2 (diff)
downloadpyramid-030d10697cc52a5c26d19818140616a485f63428.tar.gz
pyramid-030d10697cc52a5c26d19818140616a485f63428.tar.bz2
pyramid-030d10697cc52a5c26d19818140616a485f63428.zip
- Use the ``waitress`` WSGI server instead of ``wsgiref`` in scaffolding.
Diffstat (limited to 'docs/narr/project.rst')
-rw-r--r--docs/narr/project.rst32
1 files changed, 5 insertions, 27 deletions
diff --git a/docs/narr/project.rst b/docs/narr/project.rst
index 0c12d97e6..896b65249 100644
--- a/docs/narr/project.rst
+++ b/docs/narr/project.rst
@@ -888,33 +888,11 @@ Using an Alternate WSGI Server
The code generated by :app:`Pyramid` scaffolding assumes that you will be
using the ``pserve`` command to start your application while you do
-development. The default rendering of Pyramid scaffolding uses the *wsgiref*
-WSGI server, which is a server that is ill-suited for production usage: its
-main feature is that it works on all platforms and all systems, making it a
-good choice as a default server from the perspective of Pyramid's developers.
-
-To use a server more suitable for production, you have a number of choices.
-Replace the ``use = egg:pyramid#wsgref`` line in your ``production.ini`` with
-one of the following.
-
-``use = egg:Paste#http``
-
- ``paste.httpserver`` is Windows, UNIX, and Python 2 compatible. You'll
- need to ``easy_install Paste`` into your Pyramid virtualenv for this server
- to work.
-
-``use = egg:pyramid#cherrypy``
-
- The ``CherryPy`` WSGI server is Windows, UNIX, Python 2, and Python 3
- compatible. You'll need to ``easy_install CherryPy`` into your Pyramid
- virtualenv for this server to work.
-
-The servers described above are typically both faster and more secure than
-the default WSGI server used by Pyramid. Pyramid does not depend on either
-because Paste doesn't run on Python 3 (and Pyramid must) and the CherryPy
-server is not distributed separately from the CherryPy web framework (and it
-would be an awkward dependency to have a web framework rely on another web
-framework for just its server component).
+development. The default rendering of Pyramid scaffolding uses the
+*waitress* WSGI server, which is a server that is suited for production
+usage. It's not very fast, or very featureful: its main feature is that it
+works on all platforms and all systems, making it a good choice as a default
+server from the perspective of Pyramid's developers.
``pserve`` is by no means the only way to start up and serve a :app:`Pyramid`
application. As we saw in :ref:`firstapp_chapter`, ``pserve`` needn't be