Revision 11 - 2009-04-14 at 10:24:10

Deploying Catalyst Applications

Before you go automatically searching for the Apache section, stop and think: do you have a specific reason to use Apache? If not, then you might be much better off using nginx or lighttpd. They are easier to configure, faster, and consume less resources.

Here is the CPAN documentation on deployment.

Deployment without a web server

Catalyst comes with a built-in HTTP server for standalone deployment, myapp_server.pl. That server can use various engines, of which Catalyst::Engine::HTTP::Prefork is a high-performance pre-forking Catalyst engine and recommended. To serve your application with HTTP::Prefork, run:

CATALYST_ENGINE='HTTP::Prefork' script/mojomojo_server.pl

Init.d script for the standalone server

nginx

The nginx web server leads lighttpd in terms of popularity and better resource utilization, according to WikiVS.

lighttpd

The lighttpd web server is lighter, simpler and considerably faster than Apache. If you don't have a specific reason to use Apache, lighttpd will probably do the job with less headache and overhead.

Apache

Apache is the heavyweight of web servers. If you don't have a specific reason to use it (like the fact you are already using it - which most people are), go with nginx.

mod_perl vs FastCGI

FastCGI

mod_perl

FAQ

Why is my server response suddenly truncated on Ubuntu 8.04 + FastCGI (mod_fastcgi)?

Probably you are using a combination of mod_fastcgi + mod_deflate and the truncated response is compressed with mod_deflate. There is a known bug, confirmed for packages: libapache_mod_fastcgi 2.4.6 and mod_deflate from apache2 2.2.8

LiteSpeed

Installing LiteSpeed and FastCGI for Catalyst

PAR deployment

Managing FastCGI Processes

Deployment on shared hosting

My tags:
 
Popular tags:
  deployment
Powered by Catalyst
Powered by MojoMojo Hosted by Shadowcat - Managed by Nordaaker