> Or, in which of the options - there are 3 active in my current
> config. Or does it not matter which one?
OK. got it - two things...
httpd.conf must have the fqdn entered and not just the server root ip
address and the ProxyPass entries go in Virtual Hosts (Section 3)...
:)
__
> >Now we add our inverse proxy directives, within the main
> > 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 options - there are 3 a
>Now we add our inverse proxy directives, within the main
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
_
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 user.grou
> 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 ex
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]
http://lists.zope.org/mailman/listinf
