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.
In the event that all of this configuration and recompilation is not toyour taste, there is a far simpler option available to you. The niceguys at Zope.org have created a pre-compiled, pre-configured packagethat's designed to simplify Apache/Zope integration - it's called Zap("Zope plus Apache in precompiled form") and it's available for freedownload from http://www.zope.org/Download/Releases/Zap-1.1.0
This pre-compiled package comes with its own custom "httpd.conf" file,designed specifically to get the server up and running with Zope. Itcontains binary versions of both Apache and Zope, and is a breeze to setup and install, so long as there isn't any mismatch between your systemlibraries and the precompiled binaries in the Zap distribution. Check itout, if only to get a better idea of how to configure Apache to workwith Zope.
And that's about it for the moment. Whatever you've learned in thistutorial is just the tip of the iceberg - there's a lot more you can dowith the Apache/Zope combination, including running multiple Zope-basedvirtual hosts and replacing Zope's built-in authentication scheme withApache's HTTP authentication system. I'll be talking about those itemsin a follow-up piece soon - so stay tuned!
Note: All examples in this article have been tested on Linux/i586 withZope 2.5. Examples are illustrative only, and are not meant for aproduction environment. Melonfire provides no warranties or support forthe source code described in this article. YMMV!
/ 30 
