I have a Zope site which I'm doing a lot of development on, and all internal safeguards aside, I feel there's a significant chance of wrecking Zope in the process. Then it might take anywhere from hours to days to get it back up again. Although this may be sort of unlikely, it would give me some comfort to have planned for the possibility. I was wondering if there's some way I could configure Apache to fail-over to a static web site should the Zserver just stop responding (i.e. crash). Maybe this is really easy or maybe hard, but I thought someone here might know a good way. I figured it would have to have something to do with how you set up a 404 page for Apache (maybe point it to a static index page?). Is it just that simple? Or is there a smarter approach? Thanks! -- ------------------------------------------------------ Terry Hancock hancock@anansispaceworks.com Anansi Spaceworks http://www.anansispaceworks.com P.O. Box 60583 Pasadena, CA 91116-6583 ------------------------------------------------------
On Mon, 21 Jan 2002, Terry Hancock wrote:
I have a Zope site which I'm doing a lot of development on, and all internal safeguards aside, I feel there's a significant chance of wrecking Zope in the process. Then it might take anywhere from hours to days to get it back up again.
Why not just back up your Data.fs frequently? You'll only lose as much work as has been done since the last backup. -Tim -- Tim Wilson | Visit Sibley online: | Check out: Henry Sibley HS | http://www.isd197.org | http://www.zope.com W. St. Paul, MN | | http://slashdot.org wilson@visi.com | <dtml-var pithy_quote> | http://linux.com
Use Squid, set caching headers on all of your pages, and spider the site each time you bring it up. There are probably some configuration options in Squid which allows it to continue to serve content when the origin server has disappeared (if anybody knows this, I'd like to know too, so please reply if you do! ;-) - C ----- Original Message ----- From: "Terry Hancock" <hancock@anansispaceworks.com> To: <zope@zope.org> Sent: Monday, January 21, 2002 8:28 PM Subject: [Zope] Static fail-over
I have a Zope site which I'm doing a lot of development on, and all internal safeguards aside, I feel there's a significant chance of wrecking Zope in the process. Then it might take anywhere from hours to days to get it back up again.
Although this may be sort of unlikely, it would give me some comfort to have planned for the possibility.
I was wondering if there's some way I could configure Apache to fail-over to a static web site should the Zserver just stop responding (i.e. crash). Maybe this is really easy or maybe hard, but I thought someone here might know a good way. I figured it would have to have something to do with how you set up a 404 page for Apache (maybe point it to a static index page?). Is it just that simple? Or is there a smarter approach?
Thanks!
-- ------------------------------------------------------ Terry Hancock hancock@anansispaceworks.com Anansi Spaceworks http://www.anansispaceworks.com P.O. Box 60583 Pasadena, CA 91116-6583 ------------------------------------------------------
_______________________________________________ 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 )
Thanks for all the enthusiastic replies! Some of them sounded pretty scary, though, with load balancers and what not. :O I wasn't very explicit, but this is a small (one server) operation! Still, it's very interesting to look at those options, in case we do grow that big. Two specific replies... Chris McDonough wrote:
Use Squid, set caching headers on all of your pages, and spider the site each time you bring it up.
Hmm. That would be a new piece of software, but this might justify using it. I assume from what little I've heard that squid would install between Zserver and Apache in the request stream, and mostly handle caching. I like the idea of the site looking unchanged. Of course, the dynamic stuff would just fail, but I can probably find a way around that. I too would be interested in the configuration options you'd need for this. Tim Wilson wrote:
Why not just back up your Data.fs frequently? You'll only lose as much work as has been done since the last backup.
This is of course a good idea, and we do that, but it's not the data I'm worried about losing, it's face. The problem is, that during the downtime my site would look terrible (i.e. probably just a 404 Error). In a skittish market, this can have a dreadful effect on the confidence of users, customers, partners, etc. I'm thinking of maybe just creating a better error page for Apache, and maybe pursuing the Squid option as an upgrade. Thanks again! -- ------------------------------------------------------ Terry Hancock hancock@anansispaceworks.com Anansi Spaceworks http://www.anansispaceworks.com P.O. Box 60583 Pasadena, CA 91116-6583 ------------------------------------------------------
Hmm. That would be a new piece of software, but this might justify using it. I assume from what little I've heard that squid would install between Zserver and Apache in the request stream, and mostly handle caching.
You have several options here: - use Apache's mod_proxy instead of Squid (Like Squid, you'll need to see if it supports serving up content when cached content goes stale and the origin server {Zope} is unavailable). - If you aren't serving anything but Zope pages, you could replace Apache with Squid. Squid is designed to cache and IMHO does a better job than mod_proxy all around at caching. - You could arrange your network like this if you really needed Apache, but you'd still get the benefit of Squid (although more moving parts always == problems): Internet <-> Squid <-> Apache <-> Zope This setup: Internet <-> Apache <-> Squid <-> Zope ... is potentially a little more sick and twisted but would also work. - C
participants (3)
-
Chris McDonough -
Terry Hancock -
Tim Wilson