Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
show directory structure of hybrid application
  • Loading branch information
kraih committed Sep 16, 2014
1 parent a3f4fe7 commit 50dc74d
Showing 1 changed file with 21 additions and 3 deletions.
24 changes: 21 additions & 3 deletions lib/Mojolicious/Guides/Growing.pod
Expand Up @@ -523,7 +523,7 @@ And the directory structure should be looking like this now.
+- t
+- login.t

Our templates are using quite a few renderer features,
Our templates are using quite a few features of the renderer,
L<Mojolicious::Guides::Rendering> explains them all in great detail.

=head1 WELL STRUCTURED APPLICATION
Expand All @@ -540,8 +540,8 @@ directories with the command L<Mojolicious::Command::inflate>.

$ ./myapp.pl inflate

Those directories always get priority, so inflating can also be a great way to
allow your users to customize their applications.
Those directories have a higher precedence, so inflating can also be a great
way to allow your users to customize their applications.

=head2 Simplified application class

Expand Down Expand Up @@ -617,6 +617,24 @@ allow running tests again.
# Start command line interface for application
Mojolicious::Commands->start_app('MyApp');

And the directory structure of our hybrid application should be looking like
this.

myapp
|- myapp.pl
|- lib
| |- MyApp.pm
| +- MyApp
| +- Model
| +- Users.pm
|- t
| +- login.t
+- templates
|- layouts
| +- default.html.ep
|- index.html.ep
+- protected.html.ep

=head2 Controller class

Hybrid routes are a nice intermediate step, but to maximize maintainability it
Expand Down

0 comments on commit 50dc74d

Please sign in to comment.