summaryrefslogtreecommitdiff
path: root/docs/narr/project.rst
diff options
context:
space:
mode:
authorMichael Merickel <michael@merickel.org>2011-07-30 01:50:24 -0600
committerMichael Merickel <michael@merickel.org>2011-07-30 01:50:24 -0600
commit875ded31e7fdd0c85d1c91458248581b9dd729d7 (patch)
tree2063e301734ef5a79e308f67a126df48546acf07 /docs/narr/project.rst
parente1b25974a4dcc9eb9ceab70ec2276043de775f82 (diff)
downloadpyramid-875ded31e7fdd0c85d1c91458248581b9dd729d7.tar.gz
pyramid-875ded31e7fdd0c85d1c91458248581b9dd729d7.tar.bz2
pyramid-875ded31e7fdd0c85d1c91458248581b9dd729d7.zip
Updated all of the docs to reflect the new pyramid.* settings prefix.
Diffstat (limited to 'docs/narr/project.rst')
-rw-r--r--docs/narr/project.rst16
1 files changed, 8 insertions, 8 deletions
diff --git a/docs/narr/project.rst b/docs/narr/project.rst
index 5f4878470..3b1b45eda 100644
--- a/docs/narr/project.rst
+++ b/docs/narr/project.rst
@@ -472,22 +472,22 @@ represented by this entry point (``main`` in our ``__init__.py`` module).
You can provide startup-time configuration parameters to your application by
adding more settings to this section.
-The ``reload_templates`` setting in the ``[app:MyProject]`` section is a
-:app:`Pyramid` -specific setting which is passed into the framework. If it
+The ``pyramid.reload_templates`` setting in the ``[app:MyProject]`` section is
+a :app:`Pyramid` -specific setting which is passed into the framework. If it
exists, and its value is ``true``, :term:`Chameleon` and :term:`Mako`
template changes will not require an application restart to be detected. See
:ref:`reload_templates_section` for more information.
-The ``debug_templates`` setting in the ``[app:MyProject]`` section is a
+The ``pyramid.debug_templates`` setting in the ``[app:MyProject]`` section is a
:app:`Pyramid` -specific setting which is passed into the framework. If it
exists, and its value is ``true``, :term:`Chameleon` template exceptions will
contain more detailed and helpful information about the error than when
this value is ``false``. See :ref:`debug_templates_section` for more
information.
-.. warning:: The ``reload_templates`` and ``debug_templates`` options should
- be turned off for production applications, as template rendering is slowed
- when either is turned on.
+.. warning:: The ``pyramid.reload_templates`` and ``pyramid.debug_templates``
+ options should be turned off for production applications, as template
+ rendering is slowed when either is turned on.
Various other settings may exist in this section having to do with debugging
or influencing runtime behavior of a :app:`Pyramid` application. See
@@ -795,14 +795,14 @@ file call to ``add_view``).
See :ref:`views_which_use_a_renderer` for more information about how views,
renderers, and templates relate and cooperate.
-.. note:: Because our ``development.ini`` has a ``reload_templates =
+.. note:: Because our ``development.ini`` has a ``pyramid.reload_templates =
true`` directive indicating that templates should be reloaded when
they change, you won't need to restart the application server to
see changes you make to templates. During development, this is
handy. If this directive had been ``false`` (or if the directive
did not exist), you would need to restart the application server
for each template change. For production applications, you should
- set your project's ``reload_templates`` to ``false`` to increase
+ set your project's ``pyramid.reload_templates`` to ``false`` to increase
the speed at which templates may be rendered.
.. index::