5 Catalyst::Manual::Deployment - Deploying Catalyst
7 =head1 DEPLOYMENT OPTIONS
9 Catalyst applications are most often deployed as a FastCGI or mod_perl
10 application (with FastCGI being the recommended option). However, as
11 Catalyst is based on the L<PSGI> specification, any web handler
12 implementing that specification can be used to run Catalyst
15 This documentation most thoroughly covers the normal and traditional deployment
16 options, but will mention alternate methods of deployment, and we welcome
17 additional documentation from people deploying Catalyst in non-standard
20 =head2 Deployment in a shared hosting environment
22 Almost all shared hosting environments involve deploying Catalyst as a
23 FastCGI application on Apache. You will usually want to have a set of
24 libraries specific to your application installed on your shared host.
26 Full details of deploying Catalyst in a shared hosting environment are at
27 L<Catalyst::Manual::Deployment::SharedHosting>.
31 FastCGI is the most common Catalyst deployment option. It is documented
32 generally in L<Catalyst::Manual::Deployment::FastCGI>, and there are specific
33 instructions for using FastCGI with common web servers below:
37 L<Catalyst::Manual::Deployment::Apache::FastCGI>
41 L<Catalyst::Manual::Deployment::nginx::FastCGI>
45 L<Catalyst::Manual::Deployment::lighttpd::FastCGI>
49 L<Catalyst::Manual::Deployment::IIS::FastCGI>
53 Traditionally a common deployment option for dedicated applications,
54 mod_perl has some advantages and disadvantages over FastCGI. Use of
55 mod_perl is documented in
56 L<Catalyst::Manual::Deployment::Apache::mod_perl>.
58 =head2 Development Server
60 It is possible to deploy the Catalyst development server behind a
61 reverse proxy. This may work well for small-scale applications which are
62 in an early development phase, but which you want to be able to show to
63 people. See L<Catalyst::Manual::Deployment::DevelopmentServer>.
67 Catalyst can be deployed with any PSGI-compliant handler. See L<Catalyst::PSGI>
68 for more information; a list of possible deployment servers are shown
73 L<Starman> is a high-performance Perl server implementation, which is designed
74 to be used directly (rather than behind a reverse proxy). It includes HTTP/1.1
75 support, chunked requests and responses, keep-alive, and pipeline requests.
79 Starlet is a standalone HTTP/1.0 server with keepāalive support which is
80 suitable for running HTTP application servers behind a reverse proxy.
84 L<Twiggy> is a high-performance asynchronous web server. It can be used
85 in conjunction with Catalyst, but there are a number of caveats which
86 mean that it is not suitable for most deployments.
90 L<Chef|http://www.opscode.com/chef/> is an open-source systems integration
91 framework built specifically for automating cloud computing deployments. A
92 Cookbooks demonstrating how to deploy a Catalyst application using Chef is
93 available at L<http://community.opscode.com/cookbooks/catalyst> and
94 L<http://github.com/melezhik/cookbooks/wiki/Catalyst-cookbook-intro>.
98 Catalyst Contributors, see Catalyst.pm
102 This library is free software. You can redistribute it and/or modify it under
103 the same terms as Perl itself.