summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorChris McDonough <chrism@plope.com>2010-12-19 19:17:44 -0500
committerChris McDonough <chrism@plope.com>2010-12-19 19:17:44 -0500
commit8dabcb4c5e162075c3418549fc22eb5b7a55200b (patch)
tree9b104bfc13c64d7f948b2fe7775e460ff0e217aa /docs
parent53f1bb24eb51ac994185f2365930220a9d87e77e (diff)
parent7b9066cccb09d1e93df88f8b3ebc9a74ec84730c (diff)
downloadpyramid-8dabcb4c5e162075c3418549fc22eb5b7a55200b.tar.gz
pyramid-8dabcb4c5e162075c3418549fc22eb5b7a55200b.tar.bz2
pyramid-8dabcb4c5e162075c3418549fc22eb5b7a55200b.zip
Merge branch 'jahmad-typos'
Diffstat (limited to 'docs')
-rw-r--r--docs/narr/security.rst4
-rw-r--r--docs/narr/templates.rst8
-rw-r--r--docs/narr/urldispatch.rst4
-rw-r--r--docs/narr/views.rst2
4 files changed, 9 insertions, 9 deletions
diff --git a/docs/narr/security.rst b/docs/narr/security.rst
index c045e3b32..c5262faa2 100644
--- a/docs/narr/security.rst
+++ b/docs/narr/security.rst
@@ -496,12 +496,12 @@ Debugging View Authorization Failures
If your application in your judgment is allowing or denying view
access inappropriately, start your application under a shell using the
-``BFG_DEBUG_AUTHORIZATION`` environment variable set to ``1``. For
+``PYRAMID_DEBUG_AUTHORIZATION`` environment variable set to ``1``. For
example:
.. code-block:: text
- $ BFG_DEBUG_AUTHORIZATION=1 bin/paster serve myproject.ini
+ $ PYRAMID_DEBUG_AUTHORIZATION=1 bin/paster serve myproject.ini
When any authorization takes place during a top-level view rendering,
a message will be logged to the console (to stderr) about what ACE in
diff --git a/docs/narr/templates.rst b/docs/narr/templates.rst
index adec9aa0c..437b823e9 100644
--- a/docs/narr/templates.rst
+++ b/docs/narr/templates.rst
@@ -614,12 +614,12 @@ In order to turn on template exception debugging, you can use an
environment variable setting or a configuration file setting.
To use an environment variable, start your application under a shell
-using the ``BFG_DEBUG_TEMPLATES`` operating system environment
+using the ``PYRAMID_DEBUG_TEMPLATES`` operating system environment
variable set to ``1``, For example:
.. code-block:: text
- $ BFG_DEBUG_TEMPLATES=1 bin/paster serve myproject.ini
+ $ PYRAMID_DEBUG_TEMPLATES=1 bin/paster serve myproject.ini
To use a setting in the application ``.ini`` file for the same
purpose, set the ``debug_templates`` key to ``true`` within the
@@ -777,12 +777,12 @@ In order to turn on automatic reloading of templates, you can use an
environment variable, or a configuration file setting.
To use an environment variable, start your application under a shell
-using the ``BFG_RELOAD_TEMPLATES`` operating system environment
+using the ``PYRAMID_RELOAD_TEMPLATES`` operating system environment
variable set to ``1``, For example:
.. code-block:: text
- $ BFG_RELOAD_TEMPLATES=1 bin/paster serve myproject.ini
+ $ PYRAMID_RELOAD_TEMPLATES=1 bin/paster serve myproject.ini
To use a setting in the application ``.ini`` file for the same
purpose, set the ``reload_templates`` key to ``true`` within the
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
diff --git a/docs/narr/views.rst b/docs/narr/views.rst
index 447385458..1aa1eea43 100644
--- a/docs/narr/views.rst
+++ b/docs/narr/views.rst
@@ -1472,7 +1472,7 @@ for more information about changing the default notfound view.
It's useful to be able to debug :exc:`NotFound` error responses when they
occur unexpectedly due to an application registry misconfiguration. To debug
-these errors, use the ``BFG_DEBUG_NOTFOUND`` environment variable or the
+these errors, use the ``PYRAMID_DEBUG_NOTFOUND`` environment variable or the
``debug_notfound`` configuration file setting. Details of why a view was not
found will be printed to ``stderr``, and the browser representation of the
error will include the same information. See :ref:`environment_chapter` for