X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FCookbook.pod;h=07e979414a4496309a8210550d5a4adbb23332f8;hb=822fe9544767709e6d75eda2b0cbcfb46bb494dd;hp=00e8edae5922a5e5522c56b06710f583ee911aaf;hpb=2343e11777834e8785e966f572a3a0a2132c3a89;p=catagits%2FCatalyst-Runtime.git diff --git a/lib/Catalyst/Manual/Cookbook.pod b/lib/Catalyst/Manual/Cookbook.pod index 00e8eda..07e9794 100644 --- a/lib/Catalyst/Manual/Cookbook.pod +++ b/lib/Catalyst/Manual/Cookbook.pod @@ -18,10 +18,17 @@ placing a C call in the C action. die "forced debug"; } -If you're tired of removing and adding this all the time, you -can easily add a condition. For example: +If you're tired of removing and adding this all the time, you can add a +condition in the C action. For example: + + sub end : Private { + my ( $self, $c ) = @_; + die "forced debug" if $c->req->params->{dump_info}; + } + +Then just add to your query string C<"&dump_info=1">, or the like, to +force debug output. - die "force debug" if $c->req->params->{dump_info}; =head2 Disable statistics @@ -66,10 +73,16 @@ Just use Catalyst::Model::CDBI::CRUD as your base class. 1; -Modify the $c->form() parameters to match your needs, and don't forget to copy -the templates. ;) +Modify the C<$c-Eform()> parameters to match your needs, and don't +forget to copy the templates into the template root. Can't find the +templates? They were in the CRUD model distribution, so you can do +B from the CPAN shell to find them. + +Other Scaffolding modules are in development at the time of writing. -=head2 Single file upload with Catalyst +=head2 File uploads + +=head3 Single file upload with Catalyst To implement uploads in Catalyst you need to have a HTML form similiar to this: @@ -80,7 +93,8 @@ this: -It's very important not to forget C in form. Uploads will not work without this. +It's very important not to forget C in +the form. Catalyst Controller module 'upload' action: @@ -103,12 +117,11 @@ Catalyst Controller module 'upload' action: $c->stash->{template} = 'file_upload.html'; } -=head2 Multiple file upload with Catalyst +=head3 Multiple file upload with Catalyst -Code for uploading multiple files from one form needs little changes compared -to single file upload. +Code for uploading multiple files from one form needs a few changes: -Form goes like this: +The form should have this basic structure:
@@ -118,7 +131,7 @@ Form goes like this:
-Controller: +And in the controller: sub upload : Local { my ($self, $c) = @_; @@ -140,22 +153,23 @@ Controller: $c->stash->{template} = 'file_upload.html'; } -Creq->upload)> loops automatically over all file input -fields and gets input names. After that is basic file saving code, just like in -single file upload. +Creq->upload)> loops automatically over all file +input fields and gets input names. After that is basic file saving code, +just like in single file upload. -Notice: Cing might not be what you want to do, when an error occurs, but -it works as an example. A better idea would be to store error C<$!> in -$c->stash->{error} and show a custom error template displaying this message. +Notice: Cing might not be what you want to do, when an error +occurs, but it works as an example. A better idea would be to store +error C<$!> in $c->stash->{error} and show a custom error template +displaying this message. For more information about uploads and usable methods look at -C and C. +L and L. =head2 Authentication with Catalyst::Plugin::Authentication::CDBI There are (at least) two ways to implement authentication with this plugin: 1) only checking username and password; -2) checking username, password and the roles the user has +2) checking username, password, and the roles the user has For both variants you'll need the following code in your MyApp package: @@ -283,19 +297,20 @@ And this is all you need to do. =head2 Pass-through login (and other actions) -An easy way of having assorted actions that occur during the processing of -a request that are orthogonal to its actual purpose - logins, silent +An easy way of having assorted actions that occur during the processing +of a request that are orthogonal to its actual purpose - logins, silent commands etc. Provide actions for these, but when they're required for -something else fill e.g. a form variable __login and have a sub begin like so: +something else fill e.g. a form variable __login and have a sub begin +like so: -sub begin : Private { - my ($self, $c) = @_; - foreach my $action (qw/login docommand foo bar whatever/) { - if ($c->req->params->{"__${action}"}) { - $c->forward($action); + sub begin : Private { + my ($self, $c) = @_; + foreach my $action (qw/login docommand foo bar whatever/) { + if ($c->req->params->{"__${action}"}) { + $c->forward($action); + } + } } - } -} =head2 How to use Catalyst without mod_perl @@ -304,7 +319,7 @@ However sometimes mod_perl is not an option, and running under CGI is just too slow. There's also an alternative to mod_perl that gives reasonable performance named FastCGI. -B +=head3 Using FastCGI To quote from L: "FastCGI is a language independent, scalable, extension to CGI that provides high performance @@ -358,21 +373,231 @@ authentication, authorization, and access check phases. For more information see the FastCGI documentation, the C module and L. + +=head2 Serving static content -=head1 Forwarding with a parameter +Serving static content in Catalyst can be somewhat tricky; this recipe +shows one possible solution. Using this recipe will serve all static +content through Catalyst when developing with the built-in HTTP::Daemon +server, and will make it easy to use Apache to serve the content when +your app goes into production. -Sometimes you want to pass along an argument when forward to another -action. This can easily be accomplished like this: - +Static content is best served from a single directory within your root +directory. Having many different directories such as C and +C requires more code to manage, because you must separately +identify each static directory--if you decide to add a C +directory, you'll need to change your code to account for it. In +contrast, keeping all static directories as subdirectories of a main +C directory makes things much easier to manager. Here's an +example of a typical root directory structure: + + root/ + root/content.tt + root/controller/stuff.tt + root/header.tt + root/static/ + root/static/css/main.css + root/static/images/logo.jpg + root/static/js/code.js + + +All static content lives under C with everything else being +Template Toolkit files. Now you can identify the static content by +matching C from within Catalyst. + +=head3 Serving with HTTP::Daemon (myapp_server.pl) + +To serve these files under the standalone server, we first must load the +Static plugin. Install L if it's not already +installed. + +In your main application class (MyApp.pm), load the plugin: + + use Catalyst qw/-Debug FormValidator Static OtherPlugin/; + +You will also need to make sure your end method does I forward +static content to the view, perhaps like this: + + sub end : Private { + my ( $self, $c ) = @_; + + $c->forward( 'MyApp::V::TT' ) + unless ( $c->res->body || !$c->stash->{template} ); + } + +This code will only forward to the view if a template has been +previously defined by a controller and if there is not already data in +C<$c-Eres-Ebody>. + +Next, create a controller to handle requests for the /static path. Use +the Helper to save time. This command will create a stub controller as +C. + + $ script/myapp_create.pl controller Static + +Edit the file and add the following methods: + + # serve all files under /static as static files + sub default : Path('/static') { + my ( $self, $c ) = @_; + + # Optional, allow the browser to cache the content + $c->res->headers->header( 'Cache-Control' => 'max-age=86400' ); + + $c->serve_static; # from Catalyst::Plugin::Static + } + + # also handle requests for /favicon.ico + sub favicon : Path('/favicon.ico') { + my ( $self, $c ) = @_; + + $c->serve_static; + } + +You can also define a different icon for the browser to use instead of +favicon.ico by using this in your HTML header: + + + +=head3 Common problems + +The Static plugin makes use of the C package to +automatically determine MIME types. This package is notoriously +difficult to install, especially on win32 and OSX. For OSX the easiest +path might be to install Fink, then use C. Restart the server, and everything should be fine. + +Make sure you are using the latest version (>= 0.16) for best +results. If you are having errors serving CSS files, or if they get +served as text/plain instead of text/css, you may have an outdated +shared-mime-info version. You may also wish to simply use the following +code in your Static controller: + + if ($c->req->path =~ /css$/i) { + $c->serve_static( "text/css" ); + } else { + $c->serve_static; + } + +=head3 Serving with Apache + +When using Apache, you can completely bypass Catalyst and the Static +controller by intercepting requests for the C path at the +server level. All that is required is to define a DocumentRoot and add a +separate Location block for your static content. Here is a complete +config for this application under mod_perl 1.x; variations, some of +which could be simpler, are left as an exercise for the reader: + + + use lib qw(/var/www/MyApp/lib); + + PerlModule MyApp + + + ServerName myapp.example.com + DocumentRoot /var/www/MyApp/root + + SetHandler perl-script + PerlHandler MyApp + + + SetHandler default-handler + + + +=head2 Forwarding with arguments + +Sometimes you want to pass along arguments when forwarding to another +action. As of version 5.30, arguments can be passed in the call to +C; in earlier versions, you can manually set the arguments in +the Catalyst Request object: + + # version 5.30 and later: + $c->forward('/wherever', [qw/arg1 arg2 arg3/]); + + # pre-5.30 $c->req->args([qw/arg1 arg2 arg3/]); $c->forward('/wherever'); +(See L for more information on +passing arguments via C.) + +=head2 Configure your application + +You configure your application with the C method in your +application class. This can be hard-coded, or brought in from a +separate configuration file. + +=head3 Using YAML + +YAML is a method for creating flexible and readable configuration +files. It's a great way to keep your Catalyst application configuration +in one easy-to-understand location. + +In your application class (e.g. C): + + use YAML; + # application setup + __PACKAGE__->config( YAML::LoadFile(__PACKAGE__->config->{'home'} . '/myapp.yml') ); + __PACKAGE__->setup; + +Now create C in your application home: + + --- #YAML:1.0 + # DO NOT USE TABS FOR INDENTATION OR label/value SEPARATION!!! + name: MyApp + + # authentication; perldoc Catalyst::Plugin::Authentication::CDBI + authentication: + user_class: 'MyApp::M::MyDB::Customer' + user_field: 'username' + password_field: 'password' + password_hash: 'md5' + role_class: 'MyApp::M::MyDB::Role' + user_role_class: 'MyApp::M::MyDB::PersonRole' + user_role_user_field: 'person' + + # session; perldoc Catalyst::Plugin::Session::FastMmap + session: + expires: '3600' + rewrite: '0' + storage: '/tmp/myapp.session' + + # emails; perldoc Catalyst::Plugin::Email + # this passes options as an array :( + email: + - SMTP + - localhost + +This is equivalent to: + + # configure base package + __PACKAGE__->config( name => MyApp ); + # configure authentication + __PACKAGE__->config->{authentication} = { + user_class => 'MyApp::M::MyDB::Customer', + ... + }; + # configure sessions + __PACKAGE__->config->{session} = { + expires => 3600, + ... + }; + # configure email sending + __PACKAGE__->config->{email} = [qw/SMTP localhost/]; + +See also L. + =head1 AUTHOR Sebastian Riedel, C -Danijel Milicevic C -Viljo Marrandi C +Danijel Milicevic, C +Viljo Marrandi, C +Marcus Ramberg, C +Jesse Sheidlower, C +Andy Grundman, C Marcus Ramberg C +Chisel Wright C =head1 COPYRIGHT