On Wednesday 10 December 2003 04:50, J Aaron Farr wrote: > Leo has a cron job that runs every couple of hours which checks out > (does a cvs update actually) everything in the avalon-site/site module. > This is what you see on the website. So in order to do an update you > must: > > 1. Change the XML or HTML source > 2. Generate the html site (via maven usually) > 3. Replace the old HTML files in avalon-site/site with the newly > generated ones via import or copy > 4. Commit both changes to the source and the newly generated pages to > CVS (only commit what you need. No need to regenerate the whole site if > it's not necessary) > 5. Wait a couple hours to see what you messed up. :)
Is this really optimal? The phrase "[manually] replace the old HTML files ... with the newly generated...", sounds like a perfect candidate of MLMU(tm) (manual labour mess-up)... Wouldn't it be better that the cron job does all of the above, and if that takes too much CPU, make it happen less frequently? Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
