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