Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
explain how mode changes affect built-in exception and not_found pages
  • Loading branch information
kraih committed Jul 10, 2016
1 parent 242afe3 commit 6544090
Showing 1 changed file with 10 additions and 4 deletions.
14 changes: 10 additions & 4 deletions lib/Mojolicious/Guides/Tutorial.pod
Expand Up @@ -208,11 +208,15 @@ in debugging your application.

app->start;

You can even use CSS selectors with L<Mojolicious::Command::get> to extract
only the information you're actually interested in.
You can even use CSS selectors with L<Mojolicious::Command::get> to extract only
the information you're actually interested in.

$ ./myapp.pl get /dies '#error'

And don't worry about revealing too much information on these pages, they are
only available during development, and will be replaced automatically with pages
that don't reveal any sensitive information in a production environment.

=head2 Route names

All routes can have a name associated with them, this allows automatic template
Expand Down Expand Up @@ -952,8 +956,10 @@ C<log> directory exists.

$ mkdir log

Mode changes also affect a few other aspects of the framework, such as mode
specific C<exception> and C<not_found> templates.
Mode changes also affect a few other aspects of the framework, such as the
built-in C<exception> and C<not_found> pages. Once you switch modes from
C<development> to C<production>, no sensitive information will be revealed on
those pages anymore.

=head2 Testing

Expand Down

0 comments on commit 6544090

Please sign in to comment.