Can't build resource file for PCGI on Zope 2.7b1
G'day, I am installing Zope on a server whose only Python is 2.3 and which is already running Apache on port 80. Port 80 is the only one that is permitted through our local firewalls, a small but significant percentage of the audience are outside the firewall, and the system administrator (who isn't me) refuses point-blank to permit the use of mod_fastcgi or mod_proxy. So I'm trying to build Zope 2.7b1 with PCGI support. When the dust settles on the "make build; make install" there is no Zope.cgi to be seen. The file doc/WEBSERVERS.txt has the intriguing sentence: To install PCGI, please get the PCGI support package from XXX, and read the pcgi/README.txt file from that package. and then blithely describes what to do once you _have_ a Zope.cgi file to play with. Can anybody point me at the mysterious XXX, or failing that, tell me how to coerce Zope 2.7 into coughing up a Zope.cgi file? Cheers, Horatio
Unless you have a pressing reason to choose PCGI do not do it. Use RewriteRules with Apache to achieve the desired effect simpler and more efficiently. Have your Zope listen on a local port on that machine. jens On Monday, Aug 11, 2003, at 04:03 US/Eastern, Aguido Horatio Davis wrote:
G'day,
I am installing Zope on a server whose only Python is 2.3 and which is already running Apache on port 80. Port 80 is the only one that is permitted through our local firewalls, a small but significant percentage of the audience are outside the firewall, and the system administrator (who isn't me) refuses point-blank to permit the use of mod_fastcgi or mod_proxy.
So I'm trying to build Zope 2.7b1 with PCGI support. When the dust settles on the "make build; make install" there is no Zope.cgi to be seen. The file doc/WEBSERVERS.txt has the intriguing sentence:
To install PCGI, please get the PCGI support package from XXX, and read the pcgi/README.txt file from that package.
and then blithely describes what to do once you _have_ a Zope.cgi file to play with.
Can anybody point me at the mysterious XXX, or failing that, tell me how to coerce Zope 2.7 into coughing up a Zope.cgi file?
Cheers,
Horatio
On Mon, 11 Aug 2003, Jens Vagelpohl wrote:
Unless you have a pressing reason to choose PCGI do not do it. Use RewriteRules with Apache to achieve the desired effect simpler and more efficiently. Have your Zope listen on a local port on that machine.
For reasons that don't make sense to me, the local httpd is not compiled with mod_rewrite, and rebuilding it with mod_rewrite is impossible. Is PCGI being deprecated from Zope? Cheers, Horatio
Unless you have a pressing reason to choose PCGI do not do it. Use RewriteRules with Apache to achieve the desired effect simpler and more efficiently. Have your Zope listen on a local port on that machine.
For reasons that don't make sense to me, the local httpd is not compiled with mod_rewrite, and rebuilding it with mod_rewrite is impossible.
Is PCGI being deprecated from Zope?
It is not receiving much attention anymore, to put it like that. With mechanisms like mod_rewrite and mod_proxy PCGI is almost never an appropriate solution anymore. If you don't have mod_rewrite, do you have mod_proxy? Then you van use ProxyPass directives to achieve a similar effect. jens
On Mon, 2003-08-11 at 22:33, Jens Vagelpohl wrote:
Is PCGI being deprecated from Zope?
It is not receiving much attention anymore, to put it like that. With mechanisms like mod_rewrite and mod_proxy PCGI is almost never an appropriate solution anymore.
Yes, PCGI is being deprecated. Past 2.7 it will no longer available in the source distribution (nor in any binary distribution I'm aware of). - C
participants (3)
-
Aguido Horatio Davis -
Chris McDonough -
Jens Vagelpohl