X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FDeployment.pod;h=9652a435a2853ca3f98618f8f88f1b918c84fd3b;hp=745bdcf18a8bb3765845119c6d6736ecc85a37e7;hb=7e4aa7c669d1a0e4e8183c6c9186a77b0079ad3d;hpb=2d62c370d643f3abbe765aaba07ed2e188f31de7 diff --git a/lib/Catalyst/Manual/Deployment.pod b/lib/Catalyst/Manual/Deployment.pod index 745bdcf..9652a43 100644 --- a/lib/Catalyst/Manual/Deployment.pod +++ b/lib/Catalyst/Manual/Deployment.pod @@ -1,30 +1,36 @@ +=encoding utf8 + =head1 NAME Catalyst::Manual::Deployment - Deploying Catalyst =head1 DEPLOYMENT OPTIONS -Catalyst applications most often deployed as a FastCGI or mod_perl application, however -as Catalyst is based on the L specification, any web handler implementing that specification -can be used to run Catalyst applications. +Catalyst applications are most often deployed as a FastCGI or mod_perl +application (with FastCGI being the recommended option). However, as +Catalyst is based on the L specification, any web handler +implementing that specification can be used to run Catalyst +applications. -This documentation most thoroughly covers the normal and traditional deployment options, but -will mention alternate methods of deployment, and we welcome additional documentation from -people deploying Catalyst in non-standard environments. +This documentation most thoroughly covers the normal and traditional deployment +options, but will mention alternate methods of deployment, and we welcome +additional documentation from people deploying Catalyst in non-standard +environments. -=head2 Deployment for shared hosting +=head2 Deployment in a shared hosting environment -Almost all shared hosting environments involve deploying Catalyst as a FastCGI on Apache. +Almost all shared hosting environments involve deploying Catalyst as a +FastCGI application on Apache. You will usually want to have a set of +libraries specific to your application installed on your shared host. -You will usually want to have a set of libraries specific to your application installed on -your shared host, and there are instructions about -this in L. +Full details of deploying Catalyst in a shared hosting environment are at +L. =head2 FastCGI -FastCGI is the most common Catalyst deployment option, it is documented generally in -L, and there are specific instructions for common -web servers linked below: +FastCGI is the most common Catalyst deployment option. It is documented +generally in L, and there are specific +instructions for using FastCGI with common web servers below: =head3 Apache @@ -44,35 +50,48 @@ L =head2 mod_perl -Traditionally a common deployment option for dedicated applications, with some advantages and -disadvantages over FastCGI. This is documented in L. +Traditionally a common deployment option for dedicated applications, +mod_perl has some advantages and disadvantages over FastCGI. Use of +mod_perl is documented in +L. =head2 Development Server -It is possible to deploy the Catalyst development server behind a reverse proxy. This may work -well for small scale applications which are in an early development phase, but you want to be -able to show to people. See: L. +It is possible to deploy the Catalyst development server behind a +reverse proxy. This may work well for small-scale applications which are +in an early development phase, but which you want to be able to show to +people. See L. =head2 PSGI -Catalyst can be deployed with any PSGI compliant handler. See L for more information, -and a list of possible deployment servers are shown below: +Catalyst can be deployed with any PSGI-compliant handler. See L +for more information; a list of possible deployment servers are shown +below: =head3 Starman -L is a high performance pure perl server implementation, which is designed to be used -directly. - -=head3 Starlet. +L is a high-performance Perl server implementation, which is designed +to be used directly (rather than behind a reverse proxy). It includes HTTP/1.1 +support, chunked requests and responses, keep-alive, and pipeline requests. -XXX - FIXME +=head3 Starlet -+ other options? +Starlet is a standalone HTTP/1.0 server with keep‐alive support which is +suitable for running HTTP application servers behind a reverse proxy. =head3 Twiggy -L is a high-performance asynchronous web server. It can be used in conjunction with Catalyst, -but with a number of caveats which mean that it is not suitable for most deployments. +L is a high-performance asynchronous web server. It can be used +in conjunction with Catalyst, but there are a number of caveats which +mean that it is not suitable for most deployments. + +=head2 Chef + + is an open-source systems integration +framework built specifically for automating cloud computing deployments. A +Cookbooks demonstrating how to deploy a Catalyst application using Chef is +available at L and +L. =head1 AUTHORS