summaryrefslogtreecommitdiff
path: root/docs/narr/urldispatch.rst
diff options
context:
space:
mode:
authorJamaludin Ahmad <j.ahmad@gmx.net>2010-12-20 06:23:04 +0700
committerJamaludin Ahmad <j.ahmad@gmx.net>2010-12-20 06:23:04 +0700
commit7b9066cccb09d1e93df88f8b3ebc9a74ec84730c (patch)
tree400ab386b9fa316fb7303ab6a22c4809e2c6325b /docs/narr/urldispatch.rst
parenta59c789b2bb4a1de5f79537cc2f1022c97bb51f6 (diff)
downloadpyramid-7b9066cccb09d1e93df88f8b3ebc9a74ec84730c.tar.gz
pyramid-7b9066cccb09d1e93df88f8b3ebc9a74ec84730c.tar.bz2
pyramid-7b9066cccb09d1e93df88f8b3ebc9a74ec84730c.zip
BFG_ -> PYRAMID_
Diffstat (limited to 'docs/narr/urldispatch.rst')
-rw-r--r--docs/narr/urldispatch.rst4
1 files changed, 2 insertions, 2 deletions
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