svn commit: r885919 [3/3] - in /websites/staging/marmotta/trunk/content: ./ apidocs/packages dependencies.html platform/cloud.html

[bu...@apache.org]

Modified: websites/staging/marmotta/trunk/content/platform/cloud.html
==============================================================================
--- websites/staging/marmotta/trunk/content/platform/cloud.html (original)
+++ websites/staging/marmotta/trunk/content/platform/cloud.html Fri Nov  8 21:04:15 2013
@@ -400,7 +400,7 @@
 <li><tt>database.password</tt>: password for accessing the database</li>
 </ul>
 <p>When initialising the cluster for the first time, it is advisable to first start up only a single Marmotta instance to let it allow setting up the necessary database tables. When the database initialisation is complete, all other instances cam be started up in any order. When starting up a new instance, the Zookeeper module will automatically create a proper datacenter ID for generating database IDs that are unique over the cluster.</p>
-<p>When running in a high-load environment, it is also useful to startup the database in a database cluster. This is e.g. supported by PostgreSQL.</p></div>
+<p>When running in a high-load environment, it is also useful to startup the database in a database cluster. This is e.g. supported by PostgreSQL. The setup of a high-availability cluster is described in the <a class="externalLink" href="http://www.postgresql.org/docs/9.3/static/high-availability.html">PostgreSQL documentation</a>.</p></div>
 <div class="section">
 <h2>Additional Configuration<a name="Additional_Configuration"></a></h2>
 <p>For properly running Apache Marmotta in a cluster, the following additional configurations need to be considered:</p>