Hi all, I've read a bit about fastcgi, and wondered if it might be an interesting solution for e.g. running php in a user-switched environment or running ruby-on-rails etc. But I wonder why nobody (searched on Google) seems to use CentOS with mod_fastcgi for Apache 2.x. And I also wonder why people actually using Apache 2.x and ruby-on-rails with CentOS did run a lighthttpd-fastcgi inbetween and reverse-proxying requests from Apache to lighthttpd to actually forward them to RoR running as fastcgi. Could sombody please give me a hint? Regards, Michael
On Sun, 2006-03-12 at 17:33 +0100, Michael Metz wrote:> Hi all, > > I've read a bit about fastcgi, and wondered if it might be an > interesting solution for e.g. running php in a user-switched environment > or running ruby-on-rails etc. > > But I wonder why nobody (searched on Google) seems to use CentOS with > mod_fastcgi for Apache 2.x. > > And I also wonder why people actually using Apache 2.x and ruby-on-rails > with CentOS did run a lighthttpd-fastcgi inbetween and reverse-proxying > requests from Apache to lighthttpd to actually forward them to RoR > running as fastcgi. > > Could sombody please give me a hint?---- my original efforts at setting up ruby on Fedora, I used lighttpd w/fastcgi and it was fairly easy to set up. my current 'production' system is using CentOS 4 & apache w/ fastcgi and it was a little more effort to get working but it works and is fine. I really don't want to bother with also running lighthttpd at this point (and then using apache to proxy the rails stuff to lighttpd at this point, primarily because it's not an issue and I'm lazy and I believe in keep it simple). I think the reason that people do things like that is because they need to run apache on the system for some stuff which will tie up ports 80/443 and then lightty can't use them so it has to use other ports and you simply proxy the paths to the lightty application and their specific ports. This allows the speed of lightty and the user/dns simplicity of url's without using the specific port assignments which would necessarily have to be used when running lightty on a system already runing apache. Is that what you were looking for? Craig
On Sun, 2006-03-12 at 10:33, Michael Metz wrote:> I've read a bit about fastcgi, and wondered if it might be an > interesting solution for e.g. running php in a user-switched environment > or running ruby-on-rails etc. > > But I wonder why nobody (searched on Google) seems to use CentOS with > mod_fastcgi for Apache 2.x.Fastcgi hasn't been updated for a while. It does work with Centos. You can find directions for installing Request Tracker under RHEL with fastcgi here: http://wiki.bestpractical.com/index.cgi?RHEL4InstallGuide and it works equally well with Centos.> And I also wonder why people actually using Apache 2.x and ruby-on-rails > with CentOS did run a lighthttpd-fastcgi inbetween and reverse-proxying > requests from Apache to lighthttpd to actually forward them to RoR > running as fastcgi. > > Could sombody please give me a hint?I don't know anything about this particular project but there are several reasons to use a reverse-proxy front end. One is to hide the fact that you need different program instances perhaps running under different uids or with conflicting options to serve different parts of a site. Another would be to allow caching of parts of the output generated by the real server. Also, if you have clients connecting over a slow link, using a lightweight proxy can release the memory-intense server connection quickly while dribbling the results back to the client. -- Les Mikesell lesmikesell at gmail.com
On Sun, 2006-03-12 at 17:33 +0100, Michael Metz wrote:> Hi all, > > I've read a bit about fastcgi, and wondered if it might be an > interesting solution for e.g. running php in a user-switched environment > or running ruby-on-rails etc. > > But I wonder why nobody (searched on Google) seems to use CentOS with > mod_fastcgi for Apache 2.x. > > And I also wonder why people actually using Apache 2.x and ruby-on-rails > with CentOS did run a lighthttpd-fastcgi inbetween and reverse-proxying > requests from Apache to lighthttpd to actually forward them to RoR > running as fastcgi. > > Could sombody please give me a hint? > >For the record, our mirrorlist selection program uses fastcgi and lighttpd. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.centos.org/pipermail/centos/attachments/20060312/ce051d81/attachment.sig>