move all paster commands to a separate chapter

1 files changed, 3 insertions, 40 deletions

diff --git a/docs/narr/urldispatch.rst b/docs/narr/urldispatch.rst
index 52311682e..b0a7009e3 100644
--- a/docs/narr/urldispatch.rst
+++ b/docs/narr/urldispatch.rst
@@ -1028,46 +1028,9 @@ which you started the application from.  For example:
 See :ref:`environment_chapter` for more information about how, and where to
 set these values.
 
-.. index::
-   pair: routes; printing
-   single: paster proutes
-
-.. _displaying_application_routes:
-
-Displaying All Application Routes
----------------------------------
-
-You can use the ``paster proutes`` command in a terminal window to print a
-summary of routes related to your application.  Much like the ``paster
-pshell`` command (see :ref:`interactive_shell`), the ``paster proutes``
-command accepts one argument with the format ``config_file#section_name``.
-The ``config_file`` is the path to your application's ``.ini`` file,
-and ``section_name`` is the ``app`` section name inside the ``.ini`` file
-which points to your application.
-
-For example:
-
-.. code-block:: text
-   :linenos:
-
-   [chrism@thinko MyProject]$ ../bin/paster proutes development.ini#MyProject
-   Name            Pattern                        View
-   ----            -------                        ----                     
-   home            /                              <function my_view>
-   home2           /                              <function my_view>
-   another         /another                       None                     
-   static/         static/*subpath                <static_view object>
-   catchall        /*subpath                      <function static_view>
-
-``paster proutes`` generates a table.  The table has three columns: a Name
-name column, a Pattern column, and a View column.  The items listed in the
-Name column are route names, the items listen in the Pattern column are route
-patterns, and the items listed in the View column are representations of the
-view callable that will be invoked when a request matches the associated
-route pattern.  The view column may show ``None`` if no associated view
-callable could be found.  If no routes are configured within your
-application, nothing will be printed to the console when ``paster proutes``
-is executed.
+You can also use the ``paster proutes`` command to see a display of all the
+routes configured in your application; for more information, see
+:ref:`displaying_application_routes`.
 
 Route View Callable Registration and Lookup Details
 ---------------------------------------------------