Now we add our inverse proxy directives, within the main Directory
context:
ProxyPass /Zope/ http://fightclub.org:8080/
ProxyPassReverse /Zope/ http://fightclub.org:8080/
Do they mean enter this as an addition to the httpd.conf DocumentRoot tag?
Or, in which of the Directory options -
I thought I read where there is a tar ball with Zope and Apache precompiled
to work together without Zserver?
I'm on a deadline to get the demo project up and going, and not having to go
through half a day of compiling this and that would be awesome.
Any Ideas?
Rick
Well, I found it but - It's compiled against an older glibc...
Oh well. Looks like I'll miss the deadline to get the demo up, Unless
someone has some magic to pull somehow.
___
Zope maillist - [EMAIL PROTECTED]
Well, I found it but - It's compiled against an older glibc...
Oh well. Looks like I'll miss the deadline to get the demo up, Unless
someone has some magic to pull somehow.
Uncle Jonathan's Magic Zope Recipe is here ;)
- Get a binary release of Zope and unpack into
/usr/local for
Even if you compiled zope...on a PII 450 it only took a few minutes...
and the process was (minus the apache stuff)...
get source tar.gz
unpack in a location
run python w_pcgi (or python wo_pcgi) (wo or w is dependant on if you want
pcgi or not...you probably want wo_pcgi)
chown -R
Now we add our inverse proxy directives, within the main Directory
context:
ProxyPass /Zope/ http://fightclub.org:8080/
ProxyPassReverse /Zope/ http://fightclub.org:8080/
Do they mean enter this as an addition to the httpd.conf DocumentRoot tag?
Rick
