From 7b9066cccb09d1e93df88f8b3ebc9a74ec84730c Mon Sep 17 00:00:00 2001 From: Jamaludin Ahmad Date: Mon, 20 Dec 2010 06:23:04 +0700 Subject: BFG_ -> PYRAMID_ --- docs/narr/urldispatch.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/narr/urldispatch.rst') diff --git a/docs/narr/urldispatch.rst b/docs/narr/urldispatch.rst index 0d7eee7c9..504c9716d 100644 --- a/docs/narr/urldispatch.rst +++ b/docs/narr/urldispatch.rst @@ -1207,7 +1207,7 @@ Debugging Route Matching It's useful to be able to take a peek under the hood when requests that enter your application arent matching your routes as you expect them to. To debug -route matching, use the ``BFG_DEBUG_ROUTEMATCH`` environment variable or the +route matching, use the ``PYRAMID_DEBUG_ROUTEMATCH`` environment variable or the ``debug_routematch`` configuration file setting (set either to ``true``). Details of the route matching decision for a particular request to the :app:`Pyramid` application will be printed to the ``stderr`` of the console @@ -1216,7 +1216,7 @@ which you started the application from. For example: .. code-block:: text :linenos: - [chrism@thinko pylonsbasic]$ BFG_DEBUG_ROUTEMATCH=true \ + [chrism@thinko pylonsbasic]$ PYRAMID_DEBUG_ROUTEMATCH=true \ bin/paster serve development.ini Starting server in PID 13586. serving on 0.0.0.0:6543 view at http://127.0.0.1:6543 -- cgit v1.2.3