Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Wed, 16 Apr 2003 billhorne at attbi.com wrote: > With that in mind, please tell me if the CVS floating tags will allow Apache to > retrieve a web page from the "development" directory, or to default to > the "production" directory if the page isn't in development. Nope. The solution I described would be independent on Apache, and instead would depend on building a directory consisting of the union of production and pending pages appropriately. The only real issue I see with the way you're looking for is that you're showing them a fundamental performance problem. I assume that you can assume the large majority of pages are in production, not development. Therefore to look for everything in development first, you're going to generate a large majority of double requests and thus effectively halve your performance. That's why I thought it would be better to somehow use production as the default and just overlay the pending/dev content on top of that. Another post described 404 trapping. I'm not sure that you can put that much logic in Apache config, though. I thought you could only really redirect 404 to another static url. Duane > > TIA. > > Bill Horne > > Have you considered CVS and some floating tags? You could > > automate the whole process. All pages get one of the three > > tags you mentioned. Start by checking out production (with > > cvs update -rPRODUCTION -dPA to always prune old stuff), then > > update the pending tag on top of that. Once something is > > promoted out of pending, tag it as production. > > > > IF something is tagged as retired, then it won't show up in > > either phase, and thus effectively not exist unless you do a > > retired-only build. > > > > Duane > > > > On Tue, 15 Apr 2003, Bill Horne wrote:T > > > > > 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 > > > > > > > _______________________________________________ > > Discuss mailing list > > Discuss at blu.org > > http://www.blu.org/mailman/listinfo/discuss > _______________________________________________ > Discuss mailing list > Discuss at blu.org > http://www.blu.org/mailman/listinfo/discuss >
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |