Precompiled w/Apache?
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.
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 example. - Install Apache if you haven't got it already. - Do a search for 'apache' on Zope.org and locate the proxypass howto. - Read and implement proxypass. Shouldn't take more than about 30 minutes. Magic no? ;) Cya Jonathan
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.group of the account who will use zope ./start done... (I probably forgot a step...but the README/docs are very clear on how to set it up) On Wednesday 20 December 2000 12:44 pm, Jonathan \(ListServ Account\) wrote:
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 example. - Install Apache if you haven't got it already. - Do a search for 'apache' on Zope.org and locate the proxypass howto. - Read and implement proxypass.
Shouldn't take more than about 30 minutes. Magic no? ;)
Cya Jonathan
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
-- Edward Muller - edwardam@home.com - edwardam@handhelds.org 'It's because crappy programs offend me.' --Eric Raymond
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
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 - there are 3 active in my current config. Or does it not matter which one?
Or, in which of the <Directory> 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)... :)
participants (3)
-
Edward Muller -
Jonathan (ListServ Account) -
Rick Munday