Author: crossley
Date: Sun Jul 14 05:43:52 2013
New Revision: 1502941
URL: http://svn.apache.org/r1502941
Log:
Publish from forrestbot
Modified:
forrest/site/dtdx/document-v13.pdf
forrest/site/dtdx/document-v20.pdf
forrest/site/howto-forrestbot-svn.html
forrest/site/procedures/How_to_publish_docs.html
Modified: forrest/site/dtdx/document-v13.pdf
URL:
http://svn.apache.org/viewvc/forrest/site/dtdx/document-v13.pdf?rev=1502941&r1=1502940&r2=1502941&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/dtdx/document-v20.pdf
URL:
http://svn.apache.org/viewvc/forrest/site/dtdx/document-v20.pdf?rev=1502941&r1=1502940&r2=1502941&view=diff
==============================================================================
Binary files - no diff available.
Modified: forrest/site/howto-forrestbot-svn.html
URL:
http://svn.apache.org/viewvc/forrest/site/howto-forrestbot-svn.html?rev=1502941&r1=1502940&r2=1502941&view=diff
==============================================================================
--- forrest/site/howto-forrestbot-svn.html (original)
+++ forrest/site/howto-forrestbot-svn.html Sun Jul 14 05:43:52 2013
@@ -344,7 +344,10 @@ document.write("Last Published: " + docu
Our source documents are managed in the project's Subversion (SVN)
version control system. Each committer has a local SVN working copy on their
office computer. We can prepare source changes and review them with 'forrest
run' and 'forrest validate-xdocs'. When satisfied we 'svn commit' those
changes. Our Forrestbot uses the "getsrc.local" workstage to retrieve the
sources from the local svn checkout.
</p>
<p>
- The generated static documents which form the website are also stored
in SVN. So our Forrestbot uses the "deploy.svn" workstage to deploy the
generated documents. To publish the website, a regular cron job on the
apache.org server automatically does 'svn update' in the website's document
space. Elegant.
+ The generated static documents which form the website are also stored
in SVN. So our Forrestbot uses the "deploy.svn" workstage to deploy the
generated documents.
+ The svnpubsub system automatically kicks in to do the final publish
step
+ (see <a
href="http://www.apache.org/dev/project-site#intro";>explanation</a>).
+ Elegant.
</p>
<p>
That is what we call a "local forrestbot". Each committer can conduct
Modified: forrest/site/procedures/How_to_publish_docs.html
URL:
http://svn.apache.org/viewvc/forrest/site/procedures/How_to_publish_docs.html?rev=1502941&r1=1502940&r2=1502941&view=diff
==============================================================================
--- forrest/site/procedures/How_to_publish_docs.html (original)
+++ forrest/site/procedures/How_to_publish_docs.html Sun Jul 14 05:43:52 2013
@@ -289,12 +289,9 @@ forrest -f publish.xml deploy</pre>
This builds the documentation locally then deploys it by committing it
to the
<a href="http://svn.apache.org/repos/asf/forrest/site";>forrest/site
- SVN</a>. Then a cronjob on the server will automatically publish it.
- However, if quicker turnaround is required, then do this:
+ SVN</a>.
+ The svnpubsub system automatically kicks in to do the final publish
step.
</p>
-<pre class="code">ssh people.apache.org
-cd /www/forrest.apache.org
-svn update</pre>
<p>
See more detailed <a
href="../howto-forrestbot-svn.html">explanation</a> of this
procedure.
