cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven Noels <>
Subject Re: [RT] Cocoon's own publishing system
Date Tue, 11 Mar 2003 20:07:32 GMT
Stefano Mazzocchi wrote:

> 1) repository is CVS on icarus. as it is today. no changes required in 
> the editing/authoring process (for now, at least)
> 2) automated staging server is moof (or nagoya)
> I'd suggest to install it on moof (or nagoya) [moof is a macosx server 
> donated to the ASF by apple and located in their campus, lots of 
> bandwidth and support for final java 1.4.1 as for yesterday, administred 
> by the apache instrastructure]
> Checkout is done over anoncvs, so no possible compromise from the 
> staging server to the repository.
> 3) the staging server should work for docs as gump works for nightly 
> builds, nagging the appropriate mail list if:
>  - docs aren't valid
>  - links are broken
> Note that javadocs and idldocs must be automated as well.
> 4) the staging server will regenerate results automatically grabbing the 
> changes out of CVS directly. this operation will perform unassisted, 
> just like gump. in fact, forrest was born to be the gump alter-ego for 
> documentation.
> 5) when publishing on production is needed, a person with an account on 
> icarus will simply log in and perform a remote rsync between the staging 
> area and the server. A simple script with a readme will do the job. I 
> estimate it might take less than 60 seconds to update the web site this 
> way since the thruput between moof and daedalus is several Mbits.

Sounds good to me.

I learned from Ask on infrastructure@ one can do rsync without an rsync 
daemon on a server, over ssh:

rsync -avz -e ssh /orig/dir/ user@otherbox:/destination/dir/

So might as well help out as a staging server.

> NOTE: from an operativity point of view, Pier has enough karma to setup 
> everything we need on moof or nagoya, as well as providing accounts for 
> those who want to help running the staging server (I would suspect Jeff 
> and Steven to be interested in helping out, hopefully others as well). 
> We might need to post our plan of action to infrastructure@ once we 
> decide what to do, but since there are no security issues they shouldn't 
> be concerned about it (I've already discussed this architecture and 
> people didn't have objections).

You can get a playground and test staging server, accounts and whatnot 
from me until Pier has sorted out moof or upgraded nagoya.

I'm happy to trigger scripts or check on their regular operations once 
they are installed, but am a bit swamped ATM to come up with some 
scripts myself.

So anyone who wants to give it a whirl just tell me and I'll be at your 
service. Cronifying "build docs" with some nagging shouldn't be too 
hard, IIUC. And the rsync stuff has already been sorted out.


Steven Noels                  
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at  
stevenn at                stevenn at

View raw message