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