> -----Original Message----- > From: Niclas Hedhman [mailto:[EMAIL PROTECTED]
<snip/> > IMVHO, either > * Do the Maven style; Let the build tool handle the publishing > directly into the site. > OR > * Having a server side list of 'site revisions', so that when the > cron job checks out, it takes the 'last number' in that list, and one > have to update such file manually when a new site has been generated. > > Advantage of the first one is that I will have immediate feedback, and > check that the stuff went on to the site correctly, i.e. sanity-check. > > Advantage of the second, that it is very easy to revert to an older > site, i.e. remove last line in the file. There are a couple of motivations for using the current approach: 1. The generated site contents are in SVN/CVS which means we DO have a revision history of the generated site. We get automatic backups, can revert to an older version, etc. 2. With the exception of the cron job which does an "svn up", it doesn't require unix shell access for anyone else to update the site. It does require that they have SVN access. The ASF would like to get to a point where there was little to no need for individual unix accounts. 3. You don't have someone directly mucking around in the public html directory manually making changes which can immediately impact site availability. We'd like to have as few as possible people or scripts directly hit /www/avalon.apache.org Keeping those in mind, I think it would be great to have a better, faster, smoother solution. It would be nicer to just commit the XML source docs and not have to commit generated HTML, but that also requires the server to run the transformation scripts which are both much more prone to failure and also more CPU intensive than a simple "svn up." J. Aaron Farr SONY ELECTRONICS STP SYSTEMS (724) 696-7653 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
