From: Jakub Narebski <jnareb@gmail.com>
To: John Goerzen <jgoerzen@complete.org>
Cc: git@vger.kernel.org
Subject: Re: FastCGI support in gitweb
Date: Tue, 04 Mar 2008 02:11:52 -0800 (PST) [thread overview]
Message-ID: <m3od9uiyru.fsf@localhost.localdomain> (raw)
In-Reply-To: <slrnfspi8b.83u.jgoerzen@katherina.lan.complete.org>
John Goerzen <jgoerzen@complete.org> writes:
> On 2008-03-04, Jakub Narebski <jnareb@gmail.com> wrote:
>>
>>> Thanks. I didn't submit this because I couldn't fix the bugs in it.
>>> Glad you found it. I had to make many changes in a similar vein with a
>>> current gitweb version; did it work for you in its current form?
>>
>> I couldn't test it with FastCGI server, as I use Apache2, and all
>> FastCGI modules for Apache are third part modules.
>
> 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?
>> Besides, it doesn't
>> make much sense to use generic FastCGI for Perl, when there is mod_perl
>> module.
>
> 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)?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-03-04 10:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 21:34 FastCGI support in gitweb Juan Jose Comellas
2008-03-01 21:50 ` Jakub Narebski
2008-03-03 12:28 ` Sam Vilain
2008-03-04 0:19 ` Jakub Narebski
2008-03-04 3:59 ` John Goerzen
2008-03-04 10:11 ` Jakub Narebski [this message]
2008-03-04 14:48 ` John Goerzen
2008-03-04 17:22 ` Jakub Narebski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3od9uiyru.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=jgoerzen@complete.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.