Author: crossley
Date: Sun Jul 14 06:01:22 2013
New Revision: 1502943
URL: http://svn.apache.org/r1502943
Log:
Publish from forrestbot
Modified:
forrest/site/dtdx/document-v13.pdf
forrest/site/dtdx/document-v20.pdf
forrest/site/howto-forrestbot-svn.html
Modified: forrest/site/dtdx/document-v13.pdf
URL:
http://svn.apache.org/viewvc/forrest/site/dtdx/document-v13.pdf?rev=1502943&r1=1502942&r2=1502943&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=1502943&r1=1502942&r2=1502943&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=1502943&r1=1502942&r2=1502943&view=diff
==============================================================================
--- forrest/site/howto-forrestbot-svn.html (original)
+++ forrest/site/howto-forrestbot-svn.html Sun Jul 14 06:01:22 2013
@@ -345,8 +345,7 @@ document.write("Last Published: " + docu
</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.
- 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>).
+ The svnpubsub system automatically kicks in to do the final publish
step.
Elegant.
</p>
<p>
@@ -452,15 +451,10 @@ forrest -f publish.xml build</pre>
<a name="production"></a>
<h3 class="underlined_5">Moving the documents into production</h3>
<p>
- Next a cron job on the server will automatically publish it.
- However, if quicker turnaround is required, then do this:
+ Next 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>).
Essentially this monitors each project's "site" svn and publishes the changes.
</p>
-<pre class="code">ssh people.apache.org
-cd /www/forrest.apache.org
-umask 002
-svn update</pre>
<p>
- Next an rsync cronjob will publish it to the production webserver.
See other <a href="http://apache.org/dev/project-site.html";>notes</a>
about how the ASF project websites are managed.
</p>
