Skip to content

Commit

Permalink
better description for why app->start has to be the last expression
Browse files Browse the repository at this point in the history
  • Loading branch information
kraih committed Mar 19, 2016
1 parent cf9d51c commit ced5972
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 5 deletions.
2 changes: 1 addition & 1 deletion Changes
@@ -1,5 +1,5 @@

6.57 2016-03-17
6.57 2016-03-19
- Fixed a few validation bugs in Mojolicious::Validator::Validation.
(Mikey, sri)

Expand Down
12 changes: 8 additions & 4 deletions lib/Mojolicious/Guides/Tutorial.pod
Expand Up @@ -53,11 +53,15 @@ just work without commands.
$ ./myapp.pl
...List of available commands (or automatically detected environment)...

The C<app-E<gt>start> call that starts the L<Mojolicious> command system should
usually be the last expression in your application and can be customized to
override normal C<@ARGV> use.
A call to L<Mojolicious/"start"> (C<app-E<gt>start>), which starts the command
system, should usually be the last expression in your application, because the
return value can be significant.

app->start('daemon');
# Start the command system and use @ARGV to pick a command
app->start;

# Start the "daemon" command
app->start('daemon', '-l', 'http://*:8080');

=head2 Reloading

Expand Down

0 comments on commit ced5972

Please sign in to comment.