Using Zope With Apache (
Page 1 of 7 )
So you've got your Apache server serving up static HTML
content, and you've got some cool new Zope applications as well. Now, in
case you were wondering, it is possible for the twain to meet - and this
article tells you how, with a step-by-step guide to the process of
serving 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 installed
it, played with it, maybe even written a few DTML pages or created some
small Zope applications. And you're sold. You're ready to install it on
your Web site, trash your old HTML and PHP scripts, and convert
everything into Zope objects.
Whoa there, big fella. Hold on just a second.
While Zope is a remarkably full-featured solution, it's not always the
best one for a live Web site or Web application. If you're developing a
complex Web application with sophisticated business logic and lots of
interconnected routines, Zope is a great sandbox to play in. If, on the
other hand, you're merely putting up Grandma's chocolate chip cookies on
the Web, you're going to find Zope way too complex for your
relatively-simpler needs.
Luckily for you, there is a compromise. You can hook Zope up to Apache
so that you get the best of both worlds, combining Apache's legendary
stability and flexibility with Zope's everything-is-an-object paradigm
to create an efficient, scalable and robust foundation for your Web
site.
And that's where this article comes in. Over the next few pages, I will
be 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 a
working Zope 2.5 installation with super-user access.
Let's get going!
/ 30 
