summaryrefslogtreecommitdiff
path: root/docs/narr/project.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/narr/project.rst')
-rw-r--r--docs/narr/project.rst9
1 files changed, 8 insertions, 1 deletions
diff --git a/docs/narr/project.rst b/docs/narr/project.rst
index af8714573..0c12d97e6 100644
--- a/docs/narr/project.rst
+++ b/docs/narr/project.rst
@@ -283,7 +283,7 @@ For example, on UNIX:
$ ../bin/pserve development.ini --reload
Starting subprocess with file monitor
Starting server in PID 16601.
- serving on 0.0.0.0:6543 view at http://127.0.0.1:6543
+ Starting HTTP server on http://0.0.0.0:6543
For more detailed information about the startup process, see
:ref:`startup_chapter`. For more information about environment variables and
@@ -909,6 +909,13 @@ one of the following.
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).
+
``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
invoked at all to run a :app:`Pyramid` application. The use of ``pserve`` to