[ https://issues.apache.org/jira/browse/FOR-1238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440095#comment-13440095 ]
David Crossley commented on FOR-1238:
-------------------------------------
We have always had our generated documents in svn at:
http://svn.apache.org/repos/asf/forrest/site
So the switch-over should be easy. As far as i can imagine, there need not be any changes to our publishing methods.
I have now switched off the cron jobs via 'crossley' on people.apache.org
which currently do 'svn up' in /www/forrest.apache.org/ directory.
There are two additional svn checkouts for the "dtd" and "entity" sub-directories.
We do emphasise that people use the Catalog Entity Resolver for local copies:
e.g. see http://forrest.apache.org/dtd/
So we need svnpubsub to handle three things:
The forrest.apache.org/ top-level:
http://svn.apache.org/repos/asf/forrest/site
The forrest.apache.org/dtd/ directory:
http://svn.apache.org/repos/asf/forrest/trunk/main/webapp/resources/schema/dtd
The forrest.apache.org/entity/ directory: http://svn.apache.org/repos/asf/forrest/trunk/main/webapp/resources/schema/entit
y
> utilise svnpubsub for Forrest website
> -------------------------------------
>
> Key: FOR-1238
> URL: https://issues.apache.org/jira/browse/FOR-1238
> Project: Forrest
> Issue Type: Sub-task
> Components: Core operations, Documentation and website
> Reporter: David Crossley
>
> Use 'svnpubsub' for the deployment of our project website.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
David Crossley commented on FOR-1238:
-------------------------------------
We have always had our generated documents in svn at:
http://svn.apache.org/repos/asf/forrest/site
So the switch-over should be easy. As far as i can imagine, there need not be any changes to our publishing methods.
I have now switched off the cron jobs via 'crossley' on people.apache.org
which currently do 'svn up' in /www/forrest.apache.org/ directory.
There are two additional svn checkouts for the "dtd" and "entity" sub-directories.
We do emphasise that people use the Catalog Entity Resolver for local copies:
e.g. see http://forrest.apache.org/dtd/
So we need svnpubsub to handle three things:
The forrest.apache.org/ top-level:
http://svn.apache.org/repos/asf/forrest/site
The forrest.apache.org/dtd/ directory:
http://svn.apache.org/repos/asf/forrest/trunk/main/webapp/resources/schema/dtd
The forrest.apache.org/entity/ directory: http://svn.apache.org/repos/asf/forrest/trunk/main/webapp/resources/schema/entit
y
> utilise svnpubsub for Forrest website
> -------------------------------------
>
> Key: FOR-1238
> URL: https://issues.apache.org/jira/browse/FOR-1238
> Project: Forrest
> Issue Type: Sub-task
> Components: Core operations, Documentation and website
> Reporter: David Crossley
>
> Use 'svnpubsub' for the deployment of our project website.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira