16 'scripts' => \$scripts,
20 pod2usage(1) if ( $help || !$ARGV[0] );
23 Catalyst::Helper->new(
24 { '.newfiles' => !$nonew, 'scripts' => $scripts, 'short' => $short } );
25 pod2usage(1) unless $helper->mk_app( $ARGV[0] );
32 catalyst - Bootstrap a Catalyst application
36 catalyst.pl [options] application-name
39 -help display this help and exits
40 -nonew don't create a .new file where a file to be created exists
41 -scripts update helper scripts only
42 -short use short types, like C instead of Controller...
44 application-name must be a valid Perl module name and can include "::"
53 The C<catalyst.pl> script bootstraps a Catalyst application, creating a
54 directory structure populated with skeleton files.
56 The application name must be a valid Perl module name. The name of the
57 directory created is formed from the application name supplied, with double
58 colons replaced with hyphens (so, for example, the directory for C<My::App> is
61 Using the example application name C<My::App>, the application directory will
62 contain the following items:
68 a skeleton README file, which you are encouraged to expand on
72 a C<Module::Build> build script
76 a changes file with an initial entry for the creation of the application
80 an old-style MakeMaker script. Catalyst uses the C<Module::Build> system so
81 this script actually generates a Makeifle that invokes the Build script.
85 contains the application module (C<My/App.pm>) and
86 subdirectories for model, view, and controller components (C<My/App/M>,
87 C<My/App/V>, and C<My/App/C>).
91 root directory for your web document content. This is left empty.
95 a directory containing helper scripts:
99 =item C<my_app_create.pl>
101 helper script to generate new component modules
103 =item C<my_app_server.pl>
105 runs the generated application within a Catalyst test server, which can be
106 used for testing without resorting to a full-blown web server configuration.
108 =item C<my_app_cgi.pl>
110 runs the generated application as a CGI script
112 =item C<my_app_fastcgi.pl>
114 runs the generated application as a FastCGI script
117 =item C<my_app_test.pl>
119 runs an action of the generated application from the comand line.
130 The application module generated by the C<catalyst.pl> script is functional,
131 although it reacts to all requests by outputting a friendly welcome screen.
136 Neither C<catalyst.pl> nor the generated helper script will overwrite existing
137 files. In fact the scripts will generate new versions of any existing files,
138 adding the extension C<.new> to the filename. The C<.new> file is not created
139 if would be identical to the existing file.
141 This means you can re-run the scripts for example to see if newer versions of
142 Catalyst or its plugins generate different code, or to see how you may have
143 changed the generated code (although you do of course have all your code in a
144 version control system anyway, don't you ...).
150 L<Catalyst::Manual>, L<Catalyst::Manual::Intro>
154 Sebastian Riedel, C<sri@oook.de>,
155 Andrew Ford, C<A.Ford@ford-mason.co.uk>
160 Copyright 2004-2005 Sebastian Riedel. All rights reserved.
162 This library is free software, you can redistribute it and/or modify it under
163 the same terms as Perl itself.