FastCGI didn't use to need VirtualhostMonster???
I couple of years ago I set up zope using FastCGI & Apache1 and all I needed in httpd.conf was the following... FastCgiExternalServer /var/www/html/zope -socket /tmp/zope.soc -pass-header Authorization <Location /zope> SetHandler fastcgi-script </Location> When I accessed the default web host e.g. http://localhost/zope I got zope. No need to set up Virtualhostmonsters or Siteroots in Zope. It just worked. All the links magically began with http://localhost/zope. That's why I really liked the FastCGI solution over using proxypass. Now, I try the same thing with Plone & Apache 2 (which should be the same in respect of Apache/FastCGI) and all the links just begin with http://localhost. Can someone please tell me what changed between then and now. Is it Apache, FastCGI or Zope? Also, is there anyway I can get this system to work again without resorting to unsightly Virtualhostmonsters? Sorry I can't remember the exact versions of applications I was using. I think Zope 2.4 had just come out and I was using Apache 1.3.x. Today I am using latest releases with Apache 2.0.x. Thanks, SimonB
Hi Simon, Simon J. Blandford wrote:
Can someone please tell me what changed between then and now. Is it Apache, FastCGI or Zope? Also, is there anyway I can get this system to work again without resorting to unsightly Virtualhostmonsters?
I'm not sure why you don't want to use VHM here, or why you think it's ugly. I've never had /any/ luck with FastCGI, so I'm approaching this from the other end of the spectrum... In Zope (with Apache), you only need /install/ a VHM - it is 100% configuration free, and will happily sit in the root of your Zope install. In Apache, you just need a rewrite rule, which is not pretty but is not complicated either. See: - http://www.plope.com/Books/2_7Edition/VirtualHosting.stx ...for the docs. N.B. All my Apaches are 1.3.x - but I doubt if much if anything differs in 2.x... -- Regards, PhilK Email: phil@xfr.co.uk / Voicemail & Facsimile: 07092 070518 "The lyf so short, the craft so long to learne" - Chaucer
Philip Kilner wrote:
Hi Simon,
Simon J. Blandford wrote:
Can someone please tell me what changed between then and now. Is it Apache, FastCGI or Zope? Also, is there anyway I can get this system to work again without resorting to unsightly Virtualhostmonsters?
I'm not sure why you don't want to use VHM here, or why you think it's ugly. I've never had /any/ luck with FastCGI, so I'm approaching this from the other end of the spectrum...
Not sure what the situation is now but two years ago when I first tried using the "virtual site root" and proxy method there were some plug-ins/products that could not handle it. Is VHM the same? Once FastCGI was compiled it was 10x less complicated to implement than any other method. No modification was required to Zope. It just worked under http://hostname/Zope transparently with only a few extra lines in httpd.conf (as detailed in previous email). Easy!
In Zope (with Apache), you only need /install/ a VHM - it is 100% configuration free, and will happily sit in the root of your Zope install.
But does it work with 100% of the products?
In Apache, you just need a rewrite rule, which is not pretty but is not complicated either. See: -
http://www.plope.com/Books/2_7Edition/VirtualHosting.stx
...for the docs.
N.B. All my Apaches are 1.3.x - but I doubt if much if anything differs in 2.x...
Well, it looks like I'll have to bite the bullet and follow the new docs. It's only a little more hassle. I'm just curious to know if anyone remembers the old FastCGI method and what changed over the last two years to stop it working so transparently. Regards, SimonB
Simon Blandford wrote:
Not sure what the situation is now but two years ago when I first tried using the "virtual site root" and proxy method there were some plug-ins/products that could not handle it. Is VHM the same?
No.
Once FastCGI was compiled it was 10x less complicated to implement than any other method. No modification was required to Zope.
No modification is required to Zope for VHM + proxying either, and it's the wy prettymuch everyone does it now...
But does it work with 100% of the products?
I'm not aware of any products it doesn't work with. cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
Hi Chris, Chris Withers wrote:
Once FastCGI was compiled it was 10x less complicated to implement than any other method. No modification was required to Zope.
No modification is required to Zope for VHM + proxying either, and it's the wy prettymuch everyone does it now...
...and wouldn't it be faster than FastCGI in any event? (My gut feeling being that NoCGI is faster than FastCGI!) -- Regards, PhilK Email: phil@xfr.co.uk / Voicemail & Facsimile: 07092 070518 "The lyf so short, the craft so long to learne" - Chaucer
participants (4)
-
Chris Withers -
Philip Kilner -
Simon Blandford -
Simon J. Blandford