1.1 --- a/INSTALL.html	Tue Mar 24 15:44:12 2015 +0100
     1.2 +++ b/INSTALL.html	Tue Mar 24 15:44:50 2015 +0100
     1.3 @@ -252,13 +252,19 @@
     1.4  
     1.5  <h2>12. Start the sytem</h2>
     1.6  
     1.7 -<p>After <code>lf_update</code> has been executed at least once, and the webserver has been
     1.8 -restarted (using the configuration above), you should be able to access your
     1.9 -LiquidFeedback system.</p>
    1.10 +<p>After <code>lf_update</code> has been executed at least once and (in case of WebMCP 1.2.x)
    1.11 +the webserver has been restarted (using the configuration above), you should be
    1.12 +able to access your LiquidFeedback system.</p>
    1.13  
    1.14  <p>If you use WebMCP 2.x, the server is started by calling:</p>
    1.15  
    1.16  <pre><code>/opt/moonbridge/moonbridge /opt/webmcp/bin/mcp.lua /opt/webmcp/ /opt/liquid_feedback_frontend/ main myconfig
    1.17  </code></pre>
    1.18 +
    1.19 +<p>In the latter case, the Moonbridge server will open a TCP port according to
    1.20 +your configuration. Directly accessing this TCP port through your webbrowser
    1.21 +is helpful for development purposes. For real-life deployment, however, it is
    1.22 +recommended to further proxy the application (e.g. using nginx). The proxy can
    1.23 +also add HTTPS support (which is not supported by Moonbridge itself).</p>
    1.24  </body>
    1.25  </html>

     2.1 --- a/INSTALL.mkd	Tue Mar 24 15:44:12 2015 +0100
     2.2 +++ b/INSTALL.mkd	Tue Mar 24 15:44:50 2015 +0100
     2.3 @@ -253,11 +253,18 @@
     2.4  12. Start the sytem
     2.5  -------------------
     2.6  
     2.7 -After `lf_update` has been executed at least once, and the webserver has been
     2.8 -restarted (using the configuration above), you should be able to access your
     2.9 -LiquidFeedback system.
    2.10 +After `lf_update` has been executed at least once and (in case of WebMCP 1.2.x)
    2.11 +the webserver has been restarted (using the configuration above), you should be
    2.12 +able to access your LiquidFeedback system.
    2.13  
    2.14  If you use WebMCP 2.x, the server is started by calling:
    2.15  
    2.16      /opt/moonbridge/moonbridge /opt/webmcp/bin/mcp.lua /opt/webmcp/ /opt/liquid_feedback_frontend/ main myconfig
    2.17  
    2.18 +In the latter case, the Moonbridge server will open a TCP port according to
    2.19 +your configuration. Directly accessing this TCP port through your webbrowser
    2.20 +is helpful for development purposes. For real-life deployment, however, it is
    2.21 +recommended to further proxy the application (e.g. using nginx). The proxy can
    2.22 +also add HTTPS support (which is not supported by Moonbridge itself).
    2.23 +
    2.24 +