|
From: Joseph J. S. <jo...@st...> - 2004-05-24 21:36:15
|
At 11:40 AM -0700 5/24/04, Kevin Matthews wrote: >Joe, you're right about the staleness problem. If you email me the >pages (maybe as a .sit package attachment?) I'll be more than happy to >upload them. OK, I can do that, and I appreciate the offer. But... At 10:06 PM +0100 5/24/04, Dair Grant wrote: >The master copy for the page is the stuff checked in to cvs under >Documentation: they were being pushed over manually to www.quesa.org for >uploading once they'd been checked in. Ah, so I suppose I should check out the pages from CVS, edit them, check them back in, and then send the affected files to Kevin? Ah, but I read on... >At the moment <http://quesa.sourceforge.net/> redirects over to ><http://www.quesa.org/>. > >It's possible to set up the sourceforge stuff so that it grabs the pages >out of cvs nightly/on a cron job, and then serves them up as >quesa.sourceforge.net. That's probably the easiest way to handle it, as >that means you just need to check a change in and it's automatically >live. > >When that's working it would be easy enough to change the redirect to >work the other way round, i.e., www.quesa.org goes to >quesa.sourceforge.net (or is an alias for). OK, then how about this plan: 1. Turn off the redirect from sourceforge.net to quesa.org, so that we can see web pages being served by sourceforge. 2. Set up that cron job to grab the pages out of CVS. 3. Update the pages in CVS as needed (shouldn't need much in this case). 4. Make quesa.org redirect to (or an alias for) quesa.sourceforge.net. This will take a little longer than the quick fix I had in mind, but it gets us to a nice place where anyone in the project can update the web pages. Best, - Joe -- ,------------------------------------------------------------------. | Joseph J. Strout Check out the Mac Web Directory: | | jo...@st... http://www.macwebdir.com/ | `------------------------------------------------------------------' |