catalyst::manual::deployment(3pm) [debian man page]

Catalyst::Manual::Deployment(3pm)			User Contributed Perl Documentation			 Catalyst::Manual::Deployment(3pm)

NAME

       Catalyst::Manual::Deployment - Deploying Catalyst

DEPLOYMENT OPTIONS

       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 PSGI 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.

   Deployment in a shared hosting environment
       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.

       Full details of deploying Catalyst in a shared hosting environment are at Catalyst::Manual::Deployment::SharedHosting.

   FastCGI
       FastCGI is the most common Catalyst deployment option. It is documented generally in Catalyst::Manual::Deployment::FastCGI, and there are
       specific instructions for using FastCGI with common web servers below:

       Apache

       Catalyst::Manual::Deployment::Apache::FastCGI

       nginx

       Catalyst::Manual::Deployment::nginx::FastCGI

       lighttpd

       Catalyst::Manual::Deployment::lighttpd::FastCGI

       Microsoft IIS

       Catalyst::Manual::Deployment::IIS::FastCGI

   mod_perl
       Traditionally a common deployment option for dedicated applications, mod_perl has some advantages and disadvantages over FastCGI. Use of
       mod_perl is documented in Catalyst::Manual::Deployment::Apache::mod_perl.

   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 which you want to be able to show to people. See Catalyst::Manual::Deployment::DevelopmentServer.

   PSGI
       Catalyst can be deployed with any PSGI-compliant handler. See Catalyst::PSGI for more information; a list of possible deployment servers
       are shown below:

       Starman

       Starman 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.

       Starlet

       Starlet is a standalone HTTP/1.0 server with keepaXXalive support which is suitable for running HTTP application servers behind a reverse
       proxy.

       Twiggy

       Twiggy 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.

   Chef
       <LChef|http://www.opscode.com/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
       <http://community.opscode.com/cookbooks/catalyst> and http://github.com/melezhik/cookbooks/wiki/Catalyst-cookbook-intro
       <http://github.com/melezhik/cookbooks/wiki/Catalyst-cookbook-intro>.

AUTHORS

       Catalyst Contributors, see Catalyst.pm

COPYRIGHT

       This library is free software. You can redistribute it and/or modify it under the same terms as Perl itself.

perl v5.14.2							    2012-01-20					 Catalyst::Manual::Deployment(3pm)

Check Out this Related Man Page

Catalyst::Engine::PSGI(3pm)				User Contributed Perl Documentation			       Catalyst::Engine::PSGI(3pm)

NAME

       Catalyst::Engine::PSGI - PSGI engine for Catalyst

SYNOPSIS

	 # app.psgi
	 use strict;
	 use MyApp;

	 MyApp->setup_engine('PSGI');
	 my $app = sub { MyApp->run(@_) };

DESCRIPTION

       Catalyst::Engine::PSGI is a Catalyst Engine that adapts Catalyst into the PSGI gateway protocol.

COMPATIBILITY

       o   Currently this engine works with Catalyst 5.8 (Catamoose) or newer.

       o   Your application is supposed to work with any PSGI servers without any code modifications, but if your application uses
	   "$c->res->write" to do streaming write, this engine will buffer the output until your app finishes.

	   To do real streaming with this engine, you should implement an IO::Handle-like object that responds to "getline" method that returns
	   chunk or undef when done, and set that object to "$c->res->body".

	   Alternatively, it is possible to set the body to a code reference, which will be used to stream content as documented in the PSGI spec.

       o   When your application runs behind the frontend proxy like nginx or lighttpd, this Catalyst engine doesn't automatically recognize the
	   incoming headers like "X-Forwarded-For", because respecting these headers by default causes a potential security issue.

	   You have to enable Plack::Middleware::ReverseProxy or Plack::Middleware::ForwardedHeaders to automatically promote those forwarded
	   headers into "REMOTE_ADDR" hence IP address of the request.

	   ReverseProxy middleware is pretty simple and has no configuration while ForwardedHeaders allows you to configure which upstream host to
	   trust, etc.

AUTHOR

       Tatsuhiko Miyagawa <miyagawa@bulknews.net>

       Most of the code is taken and modified from Catalyst::Engine::CGI.

LICENSE

       This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

SEE ALSO

       Catalyst::Engine PSGI Plack

perl v5.12.3							    2011-06-11					       Catalyst::Engine::PSGI(3pm)

Linux and UNIX Man Pages

catalyst::manual::deployment(3pm) [debian man page]

Check Out this Related Man Page