My, Apache sure can be a little tricky to configure. Following a few tips from Ben Laurie I've just built myself a minimalist Apache / Catalyst / FastCGI configuration:
Listen 8081 ErrorLog manatee_error.log PidFile manatee_httpd.pid LockFile manatee_accept.lock LoadModule alias_module /usr/lib/apache2/modules/mod_alias.so LoadModule fastcgi_module /usr/lib/apache2/modules/mod_fastcgi.so LoadModule mime_module /usr/lib/apache2/modules/mod_mime.so TypesConfig /etc/mime.types DocumentRoot /mnt/app/manatee/root Alias /static /mnt/app/manatee/root/static FastCgiIpcDir /mnt/app/manatee/tmp FastCgiServer /mnt/app/manatee/script/manatee_fastcgi.pl -processes 3 Alias / /mnt/app/manatee/script/manatee_fastcgi.pl/
That's it! Nice and low memory usage too...
Re:modperl?
acme on 2007-12-05T14:21:42
The Catalyst Cookbook has a section on this. On one side, mod_perl is very bloated. On the other, why invent another protocol when HTTP will do.Re:modperl?
perrin on 2007-12-09T20:37:31
Where's this "bloated" idea coming from? The parts of mod_perl that you don't use shouldn't get in your way. The normal way of deploying it (front-end proxy server + mod_perl app server) is functionally identical to FastCGI.Re:modperl?
deepfryed on 2007-12-19T19:32:14
and better may I say. The *only* advantage I see for fastcgi is for deploying multiple applications (written in different languages) through one webserver providing a more complex service.
Re:lighttpd?
markjugg on 2008-04-11T21:28:46
Any particular reason you do use lighttpd?Re:lighttpd?
stu42j on 2008-04-11T21:36:08
Actually, I don't. It is just that the configuration described here seems to be exactly the kind of thing lighttpd is good at. If you are comfortable with Apache, I'm not sure there is any particularly good reason to switch.