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.
So you've read the advertising, heard all your friends talking about it,and finally decided to download your own copy of Zope. You've installedit, played with it, maybe even written a few DTML pages or created somesmall Zope applications. And you're sold. You're ready to install it onyour Web site, trash your old HTML and PHP scripts, and converteverything into Zope objects.
Whoa there, big fella. Hold on just a second.
While Zope is a remarkably full-featured solution, it's not always thebest one for a live Web site or Web application. If you're developing acomplex Web application with sophisticated business logic and lots ofinterconnected routines, Zope is a great sandbox to play in. If, on theother hand, you're merely putting up Grandma's chocolate chip cookies onthe Web, you're going to find Zope way too complex for yourrelatively-simpler needs.
Luckily for you, there is a compromise. You can hook Zope up to Apacheso that you get the best of both worlds, combining Apache's legendarystability and flexibility with Zope's everything-is-an-object paradigmto create an efficient, scalable and robust foundation for your Website.
And that's where this article comes in. Over the next few pages, I willbe discussing the myriad ways in which Apache can be connected to Zope,together with my experiences on how easy or difficult each technique is.I will assume here that you're working on a Linux box, and have aworking Zope 2.5 installation with super-user access.