cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Mazzocchi <stef...@apache.org>
Subject Re: [RT] Cocoon's own publishing system
Date Wed, 12 Mar 2003 10:37:38 GMT
Steven Noels wrote:

> 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 cocoondev.org might as well help out as a staging server.

Oh, yes, totally!

>> 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.

+1

> 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.

No prob.

> 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.

So, should we perform 'forrestization' of our documents to go ahead with 
the plan?

S.


Mime
View raw message