Re: FastCGI support in gitweb

From: John Goerzen <jgoerzen@complete.org>
Date: Mar 4, 2008, 14:48 UTC
Message-ID: <slrnfsqoai.njm.jgoerzen@katherina.lan.complete.org>
In-Reply-To: <m3od9uiyru.fsf@localhost.localdomain>

On 2008-03-04, Jakub Narebski <jnareb@gmail.com> wrote:

Show 7 quoted lines

>> On Debian, this was as easy as apt-get install libapache2-mod-fcgid
>
> And for Fedora Core?
>
> From what I have found there exists three 3rd-party (i.e. not
> developed by Apache) modules for FastCGI support: mod_fastcgi,
> mod_fcgi and mod_proxy_fcgi. Which one to choose?

I like mod_fcgid, but that's just me.

Show 10 quoted lines

>> Sure it can.  I currently am running both Python and Ruby code under
>> FastCGI.  Adding mod_perl for just one program increases my
>> webserver's memory footprint, potentially dramatically, and increases
>> my complexity as well.  I'd much rather run FastCGI than mod_perl.
>
> Well, if you are running FastCGI for other scripts, it makes sense
> then.
>
> Although... doesn't there exists modules for Python (mod_python,
> mod_wsgi, mod_snake) and for Ruby (mod_ruby)?

Sure. But think of the horrendous memory footprint if I have mod_php, mod_python, mod_perl, and mod_ruby all loaded into Apache at once! (I do have mod_php in my installation) Remember that if it is configured that way, *each* Apache process/thread carries the module for PHP, Python, Perl, AND Ruby, even if it uses none of them. I've been there, done that, and it's not pretty.

FastCGI is much, much lighter on resource requirements if you are deploying apps written in various languages on a single server. Sometimes even if you aren't.

-- John