Concatenating production and change libraries for a web site

[scottprive at earthlink.net (Scott Prive)]

If you use a consistent path/name scheme, you should be able to process a
URL and always know where the "evil twin" lives (if they exist at all).
example:

/pending/results.html
/production/results.html

Then you'll need to modify the 404 error processor, so it does something
like this:

Serve /new/results.html... but if the file does not exist, it triggers the
404. Modify the 404 error script:
    if (REQUEST matches "pending") {
        $retryurl = REQUEST
        $retryurl = s/pending/production/    # OK, try production
        GET $retryurl
    } else{
        #standard 404 handling
    }

I've seen this done, and I believe it was in the 404 handler. By now there
might be an Apache module for it, but I don't know of one.

-Scott













----- Original Message -----
From: "Bill Horne" <bill at horne.net>
To: "BLU Discussion List" <discuss at blu.org>
Sent: Tuesday, April 15, 2003 8:57 PM
Subject: Concatenating production and change libraries for a web site


> Thanks for reading this.
>
> I run a small web site for my son's Boy Scout troop, and I'd like to
> set up a change control process that includes different directories for
> "production", "pending", and "retired" web pages.
>
> Of course, the actual site won't have this: I'm setting it up on the
> testbed platform, which is my home server.
>
> Here's what I'd like to do: I want Apache to look in the "pending"
> directory for pages, and then in the "production" directory, so that
> only web pages that are actually being worked on need to be in the
> "pending" directory. Other than a whole bunch of symlinks, how can
> I accomplish this?
>
> Thanks in advance for your help.
>
> Bill Horne
> _______________________________________________
> Discuss mailing list
> Discuss at blu.org
> http://www.blu.org/mailman/listinfo/discuss