# HG changeset patch
# User bsw
# Date 1427208290 -3600
# Node ID c43fdf63fee0aeb7aaac6775f28359d62ef20044
# Parent  51a17a0e26e9693dbf8b3f505939b753dfb09229# Parent  ee63ad6bb3e3f6b739073bfbf7ea69122ef89f54
merge

diff -r 51a17a0e26e9 -r c43fdf63fee0 INSTALL.html
--- a/INSTALL.html	Tue Mar 24 15:44:12 2015 +0100
+++ b/INSTALL.html	Tue Mar 24 15:44:50 2015 +0100
@@ -252,13 +252,19 @@
 
 <h2>12. Start the sytem</h2>
 
-<p>After <code>lf_update</code> has been executed at least once, and the webserver has been
-restarted (using the configuration above), you should be able to access your
-LiquidFeedback system.</p>
+<p>After <code>lf_update</code> has been executed at least once and (in case of WebMCP 1.2.x)
+the webserver has been restarted (using the configuration above), you should be
+able to access your LiquidFeedback system.</p>
 
 <p>If you use WebMCP 2.x, the server is started by calling:</p>
 
 <pre><code>/opt/moonbridge/moonbridge /opt/webmcp/bin/mcp.lua /opt/webmcp/ /opt/liquid_feedback_frontend/ main myconfig
 </code></pre>
+
+<p>In the latter case, the Moonbridge server will open a TCP port according to
+your configuration. Directly accessing this TCP port through your webbrowser
+is helpful for development purposes. For real-life deployment, however, it is
+recommended to further proxy the application (e.g. using nginx). The proxy can
+also add HTTPS support (which is not supported by Moonbridge itself).</p>
 </body>
 </html>
diff -r 51a17a0e26e9 -r c43fdf63fee0 INSTALL.mkd
--- a/INSTALL.mkd	Tue Mar 24 15:44:12 2015 +0100
+++ b/INSTALL.mkd	Tue Mar 24 15:44:50 2015 +0100
@@ -253,11 +253,18 @@
 12. Start the sytem
 -------------------
 
-After `lf_update` has been executed at least once, and the webserver has been
-restarted (using the configuration above), you should be able to access your
-LiquidFeedback system.
+After `lf_update` has been executed at least once and (in case of WebMCP 1.2.x)
+the webserver has been restarted (using the configuration above), you should be
+able to access your LiquidFeedback system.
 
 If you use WebMCP 2.x, the server is started by calling:
 
     /opt/moonbridge/moonbridge /opt/webmcp/bin/mcp.lua /opt/webmcp/ /opt/liquid_feedback_frontend/ main myconfig
 
+In the latter case, the Moonbridge server will open a TCP port according to
+your configuration. Directly accessing this TCP port through your webbrowser
+is helpful for development purposes. For real-life deployment, however, it is
+recommended to further proxy the application (e.g. using nginx). The proxy can
+also add HTTPS support (which is not supported by Moonbridge itself).
+
+