Commit | Line | Data |
01b62b15 |
1 | =head1 NAME |
2 | |
3 | Catalyst::Manual::Deployment - Deploying Catalyst |
4 | |
0e8eed8e |
5 | =head1 DEPLOYMENT OPTIONS |
01b62b15 |
6 | |
5abded07 |
7 | Catalyst applications are most often deployed as a FastCGI or mod_perl |
8 | application (with FastCGI being the recommended option). However, as |
9 | Catalyst is based on the L<PSGI> specification, any web handler |
10 | implementing that specification can be used to run Catalyst |
11 | applications. |
0e8eed8e |
12 | |
506ff3c8 |
13 | This documentation most thoroughly covers the normal and traditional deployment |
14 | options, but will mention alternate methods of deployment, and we welcome |
15 | additional documentation from people deploying Catalyst in non-standard |
16 | environments. |
0e8eed8e |
17 | |
5abded07 |
18 | =head2 Deployment in a shared hosting environment |
2d62c370 |
19 | |
5abded07 |
20 | Almost all shared hosting environments involve deploying Catalyst as a |
21 | FastCGI application on Apache. You will usually want to have a set of |
22 | libraries specific to your application installed on your shared host. |
01b62b15 |
23 | |
f1cee32e |
24 | Full details of deploying Catalyst in a shared hosting environment are at |
506ff3c8 |
25 | L<Catalyst::Manual::Deployment::SharedHosting>. |
01b62b15 |
26 | |
0e8eed8e |
27 | =head2 FastCGI |
28 | |
5abded07 |
29 | FastCGI is the most common Catalyst deployment option. It is documented |
506ff3c8 |
30 | generally in L<Catalyst::Manual::Deployment::FastCGI>, and there are specific |
5abded07 |
31 | instructions for using FastCGI with common web servers below: |
01b62b15 |
32 | |
0e8eed8e |
33 | =head3 Apache |
01b62b15 |
34 | |
35 | L<Catalyst::Manual::Deployment::Apache::FastCGI> |
36 | |
0e8eed8e |
37 | =head3 nginx |
38 | |
39 | L<Catalyst::Manual::Deployment::nginx::FastCGI> |
40 | |
41 | =head3 lighttpd |
42 | |
43 | L<Catalyst::Manual::Deployment::lighttpd::FastCGI> |
44 | |
45 | =head3 Microsoft IIS |
46 | |
47 | L<Catalyst::Manual::Deployment::IIS::FastCGI> |
48 | |
2d62c370 |
49 | =head2 mod_perl |
50 | |
5abded07 |
51 | Traditionally a common deployment option for dedicated applications, |
52 | mod_perl has some advantages and disadvantages over FastCGI. Use of |
53 | mod_perl is documented in |
506ff3c8 |
54 | L<Catalyst::Manual::Deployment::Apache::mod_perl>. |
2d62c370 |
55 | |
0e8eed8e |
56 | =head2 Development Server |
57 | |
5abded07 |
58 | It is possible to deploy the Catalyst development server behind a |
59 | reverse proxy. This may work well for small-scale applications which are |
60 | in an early development phase, but which you want to be able to show to |
61 | people. See L<Catalyst::Manual::Deployment::DevelopmentServer>. |
0e8eed8e |
62 | |
63 | =head2 PSGI |
01b62b15 |
64 | |
5abded07 |
65 | Catalyst can be deployed with any PSGI-compliant handler. See L<Catalyst::PSGI> |
66 | for more information; a list of possible deployment servers are shown |
506ff3c8 |
67 | below: |
2d62c370 |
68 | |
69 | =head3 Starman |
70 | |
5abded07 |
71 | L<Starman> is a high-performance Perl server implementation, which is designed |
506ff3c8 |
72 | to be used directly (rather than behind a reverse proxy). It includes HTTP/1.1 |
5abded07 |
73 | support, chunked requests and responses, keep-alive, and pipeline requests. |
2d62c370 |
74 | |
5abded07 |
75 | =head3 Starlet |
2d62c370 |
76 | |
506ff3c8 |
77 | Starlet is a standalone HTTP/1.0 server with keepāalive support which is |
78 | suitable for running HTTP application servers behind a reverse proxy. |
2d62c370 |
79 | |
80 | =head3 Twiggy |
81 | |
5abded07 |
82 | L<Twiggy> is a high-performance asynchronous web server. It can be used |
83 | in conjunction with Catalyst, but there are a number of caveats which |
84 | mean that it is not suitable for most deployments. |
2d62c370 |
85 | |
815bcace |
86 | =head2 Chef |
87 | |
88 | <LChef|http://www.opscode.com/chef/> is an open-source systems integration |
89 | framework built specifically for automating cloud computing deployments. A |
90 | Cookbooks demonstrating how to deploy a Catalyst application using Chef is |
91 | available at L<http://community.opscode.com/cookbooks/catalyst> and |
92 | L<http://github.com/melezhik/cookbooks/wiki/Catalyst-cookbook-intro>. |
93 | |
01b62b15 |
94 | =head1 AUTHORS |
95 | |
96 | Catalyst Contributors, see Catalyst.pm |
97 | |
98 | =head1 COPYRIGHT |
99 | |
100 | This library is free software. You can redistribute it and/or modify it under |
101 | the same terms as Perl itself. |
102 | |
103 | =cut |
19a5b486 |
104 | |