Skip to content

Add some clarification to Quick Tour Working with Environments #2674

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 1, 2013
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 8 additions & 5 deletions quick_tour/the_big_picture.rst
Original file line number Diff line number Diff line change
Expand Up @@ -385,16 +385,19 @@ is the developer's best friend.
.. image:: /images/quick_tour/web_debug_toolbar.png
:align: center

But what you see initially is only the tip of the iceberg; click on the weird
hexadecimal number to reveal yet another very useful Symfony2 debugging tool:
the profiler.
But what you see initially is only the tip of the iceberg; click on the long
hexadecimal number (the session token) to reveal yet another very useful
Symfony2 debugging tool: the profiler.

.. image:: /images/quick_tour/profiler.png
:align: center

Of course, you won't want to show these tools when you deploy your application
to production. That's why you will find another front controller in the
``web/`` directory (``app.php``), which is optimized for the production environment:
``web/`` directory (``app.php``), which is optimized for the production environment.
The ``AcmeDemoBundle`` is normally only available in the dev environment (see
the note below), but if you were to add it to the production environment, you
could go here:

.. code-block:: text

Expand All @@ -407,7 +410,7 @@ And if you use Apache with ``mod_rewrite`` enabled, you can even omit the

http://localhost/Symfony/web/demo/hello/Fabien

Last but not least, on the production servers, you should point your web root
Last but not least, on production servers, you should point your web root
directory to the ``web/`` directory to secure your installation and have an
even better looking URL:

Expand Down