You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by David Crossley <cr...@apache.org> on 2008/10/02 09:35:14 UTC

New docs: deploy documentation with Forrestbot "svn" or "scp"

Don't know if people saw the two new Howto documents
committed recently:

 How to deploy documentation with the Forrestbot "svn" workstage
 http://forrest.apache.org/howto-forrestbot-svn.html

This explains the example of the Forrest project's
own documentation. Other projects that use SVN to store
the generated documents will find this useful.

 How to deploy documentation with the Forrestbot "scp" workstage
 http://forrest.apache.org/howto-forrestbot-scp.html

This explains how i manage the website of a client.
It deploys the documentation to a "stage" directory
on our webserver. The client can then review it in a
private place. When satisfied, we ssh to the server
and copy it all up one directory.

This also explains the use of the Apache Cocoon
"checksums" facility to only process and deploy the
changed files.

-David

Re: New docs: deploy documentation with Forrestbot "svn" or "scp"

Posted by Thorsten Scherler <th...@juntadeandalucia.es>.
On Thu, 2008-10-02 at 17:35 +1000, David Crossley wrote:
> Don't know if people saw the two new Howto documents
> committed recently:

Nice thanks very much.

salu2

> 
>  How to deploy documentation with the Forrestbot "svn" workstage
>  http://forrest.apache.org/howto-forrestbot-svn.html
> 
> This explains the example of the Forrest project's
> own documentation. Other projects that use SVN to store
> the generated documents will find this useful.
> 
>  How to deploy documentation with the Forrestbot "scp" workstage
>  http://forrest.apache.org/howto-forrestbot-scp.html
> 
> This explains how i manage the website of a client.
> It deploys the documentation to a "stage" directory
> on our webserver. The client can then review it in a
> private place. When satisfied, we ssh to the server
> and copy it all up one directory.
> 
> This also explains the use of the Apache Cocoon
> "checksums" facility to only process and deploy the
> changed files.
> 
> -David
-- 
Thorsten Scherler                                 thorsten.at.apache.org
Open Source Java                      consulting, training and solutions