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 08:44:18 +1100
From: David Crossley <crossley@apache.org>
To: dev@forrest.apache.org
Subject: Re: Our doc deployment process
Message-ID: <20060117214418.GA3408@igg.indexgeo.com.au>
References: <1137058396.8452.15.camel@localhost> <43C62AE9.8060400@apache.org>
 <1137522997.8256.90.camel@localhost> <43CD5045.6020908@apache.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <43CD5045.6020908@apache.org>
User-Agent: Mutt/1.4i

Ross Gardler wrote:
> Thorsten Scherler wrote:
> >Ross Gardler escribi??:
> >
> >>You cannot deploy the docs automatically due to security restrictions
> >>in 
> >>the ASF. What you can do is deploy to a staging server.
> >
> >does that mean I cannot use forrest from my zone account to deploy the
> >official documentation? Only to the staging server?
> 
> Correct.
> 
> >How is David doing this? 
> 
> See our web deployment instructions in the etc folder.
> 
> We deploy to SVN, the live server then updates from there every four hours.
> 
> 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.

-David