Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Concatenating production and change libraries for a web site



Duane,

Thanks for your input. I'll add some information, and then ask a question or 
two.

The troop's goal for the web site is that it be maintained by the scouts, not 
an adult, and the raison d'etre for the separate directories is to introduce 
them to change control in general, and to (if possible) allow them to see the 
results of their efforts without having to roll a development library into 
production. In other words, we want them to be able to make mistakes, and to be 
able to correct them without an adult having to intervene, or even knowing that 
they occured ;-J.

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.

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




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org