Stefano Bagnara wrote:
> Otherwise we could at least put a cron for "svn update" of the published
> copy.
> About automatic commit to site/www of the generated site this is more
> delicate as it involve a commit, but we could even do this.
That would be considered a really bad idea. We're required to review
changes, and automation of that nature would bypass the required human
element.
> if we change things that generate changes in all html files we'll
> change a lot of files every time
> Instead I would try to start a continuos integration project for
> server+jspf+site and have a live updated site for our trunks as
> a tool for us.
How does this help? We're still generating all of the pages.
> Again I don't know if the ASF policy allow me to do this on my minotaur
> home.
In addition to the whole automation issue, you'd be consuming massive
resources on a shared system.
But so you know, the proposed ASF-wide solution is similar: a site-build
server on which projects could build and maintain their site (a staging copy
for review, and an approved copy by for pushing to the web servers). Most
discussion on this, which has frustratingly yet to jell, takes place on
[EMAIL PROTECTED]
--- Noel
