So you've got your Apache server serving up static HTMLcontent, and you've got some cool new Zope applications as well. Now, incase you were wondering, it is possible for the twain to meet - and thisarticle tells you how, with a step-by-step guide to the process ofserving up your Zope content through Apache.
Of course, there are other ways to get Zope and Apache talking as well.One of the most interesting involves using Apache's proxy module totransparently pass Zope requests to the ZServer.
The first step is to make sure that your Apache build includes supportfor the proxy module (look for "mod_proxy.c" in the output of "httpd-l"). If it doesn't, you can recompile Apache by doing the following:
$ cd /tmp/sources
$ tar -xzvf apache_1.3.20.tar.gz
$ cd apache_1.3.20
$ ./configure --enable-module=proxy
$ make
$ make install
Once the program has been installed, pop open "httpd.conf" and add thefollowing lines to it:
This tells the server to intercept all requests for the URL /community(the first argument to ProxyPass), and redirect them to the Zope server(the second argument).
While this approach is simple, it does have a few glitches. Take a lookat http://www.zope.org/Members/anser/apache_zserver for a detailedexplanation of these problems, together with some very elegant hacksthat solve them quite well.
/ 30 
