Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Date: Wed, 18 Jan 2006 10:04:02 +1100
From: David Crossley <crossley@apache.org>
To: dev@forrest.apache.org
Subject: Re: Our doc deployment process
Message-ID: <20060117230402.GB6230@igg.indexgeo.com.au>
References: <1137058396.8452.15.camel@localhost> <43C62AE9.8060400@apache.org>
 <1137522997.8256.90.camel@localhost> <43CD5045.6020908@apache.org>
 <20060117214418.GA3408@igg.indexgeo.com.au> <43CD7569.1070708@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43CD7569.1070708@apache.org>
User-Agent: Mutt/1.4i

Ross Gardler wrote:
> David Crossley wrote:
> >Ross Gardler wrote:
> >>
> >>It would be possible to make the forrestbot deploy automatically to the 
> >>svn server (in fact we use the forrestbot to do it manually).
> >
> >Except for one thing. It needs to be a committer doing
> >the svn checkin, not a role-based account.
> 
> Ahhh... yes - I *always* forget that (not a problem in some 
> environments, but it is a problem here at the ASF and I'm not at all 
> sure how it could be solved here).
> 
> It is technically possible, but it means leaving a file with username 
> and password with SVN commit access on the zone. Obviously, this is not 
> a good idea from a security perspective.

This is one of the factors that contributes to the
quagmire of site-build discussions at site-dev@

Actually we should not assume about this role-based
accounts. This was from the situation long ago when
we were not running on ASF hardware. Jeff had set up
a forrestbot at cocoondev.org - a remote machine.
Perhaps we should bring it up again on site-dev.
;-)

-David