1.1 --- a/INSTALL.html	Wed Apr 15 12:26:31 2015 +0200
     1.2 +++ b/INSTALL.html	Wed Apr 15 12:27:54 2015 +0200
     1.3 @@ -20,9 +20,10 @@
     1.4  <li>postgresql</li>
     1.5  <li>libpq-dev</li>
     1.6  <li>lighttpd (only for WebMCP 1.2.x support)</li>
     1.7 +<li>pmake or bmake (only for WebMCP 2.x with Moonbridge)</li>
     1.8  <li>imagemagick</li>
     1.9  <li>exim4</li>
    1.10 -<li>markdown2 (install with Python's pip)</li>
    1.11 +<li>markdown2 (<code>apt-get install python-pip; pip install markdown2</code>)</li>
    1.12  </ul>
    1.13  
    1.14  <p>If you're using any other Linux distribution or BSD system, install the
    1.15 @@ -35,14 +36,8 @@
    1.16  executing PostgreSQL's shell command <code>createuser</code> as database superuser
    1.17  (usually <code>pgsql</code>, or <code>postgres</code> for Debian installations):</p>
    1.18  
    1.19 -<pre><code>su - postgres
    1.20 -createuser
    1.21 -
    1.22 -Enter name of role to add: www-data
    1.23 -Shall the new role be a superuser? (y/n) n
    1.24 -Shall the new role be allowed to create databases? (y/n) y
    1.25 -Shall the new role be allowed to create more new roles? (y/n) n
    1.26 -
    1.27 +<pre><code>su postgres -s $SHELL
    1.28 +createuser --no-superuser --createdb --no-createrole www-data
    1.29  exit
    1.30  </code></pre>
    1.31  
    1.32 @@ -60,7 +55,7 @@
    1.33  make
    1.34  mkdir /opt/liquid_feedback_core
    1.35  cp core.sql lf_update lf_update_issue_order /opt/liquid_feedback_core
    1.36 -su - www-data
    1.37 +su www-data -s $SHELL
    1.38  cd /opt/liquid_feedback_core
    1.39  createdb liquid_feedback
    1.40  createlang plpgsql liquid_feedback  # command may be omitted, depending on PostgreSQL version
    1.41 @@ -225,9 +220,9 @@
    1.42  echo "${PID}" &gt; "${PIDFILE}"
    1.43  
    1.44  while true; do
    1.45 -  su - www-data -c 'nice /opt/liquid_feedback_core/lf_update dbname=liquid_feedback 2&gt;&amp;1 | logger -t "lf_updated"'
    1.46 -  su - www-data -c 'nice /opt/liquid_feedback_core/lf_update_issue_order dbname=liquid_feedback 2&gt;&amp;1 | logger -t "lf_updated"'
    1.47 -  su - www-data -c 'nice /opt/liquid_feedback_core/lf_update_suggestion_order dbname=liquid_feedback 2&gt;&amp;1 | logger -t "lf_updated"'
    1.48 +  su - www-data -s /bin/sh -c 'nice /opt/liquid_feedback_core/lf_update dbname=liquid_feedback 2&gt;&amp;1 | logger -t "lf_updated"'
    1.49 +  su - www-data -s /bin/sh -c 'nice /opt/liquid_feedback_core/lf_update_issue_order dbname=liquid_feedback 2&gt;&amp;1 | logger -t "lf_updated"'
    1.50 +  su - www-data -s /bin/sh -c 'nice /opt/liquid_feedback_core/lf_update_suggestion_order dbname=liquid_feedback 2&gt;&amp;1 | logger -t "lf_updated"'
    1.51    sleep 5
    1.52  done
    1.53  </code></pre>
    1.54 @@ -245,12 +240,12 @@
    1.55  <code>lf_update_suggestion_order</code>, the following commands should be executed in
    1.56  background:</p>
    1.57  
    1.58 -<pre><code>su - www-data
    1.59 +<pre><code>su www-data -s $SHELL
    1.60  cd /opt/liquid_feedback_frontend/
    1.61  echo "Event:send_notifications_loop()" | ../webmcp/bin/webmcp_shell myconfig
    1.62  </code></pre>
    1.63  
    1.64 -<h2>12. Start the sytem</h2>
    1.65 +<h2>12. Start the system</h2>
    1.66  
    1.67  <p>After <code>lf_update</code> has been executed at least once and (in case of WebMCP 1.2.x)
    1.68  the webserver has been restarted (using the configuration above), you should be
    1.69 @@ -258,13 +253,30 @@
    1.70  
    1.71  <p>If you use WebMCP 2.x, the server is started by calling:</p>
    1.72  
    1.73 -<pre><code>/opt/moonbridge/moonbridge /opt/webmcp/bin/mcp.lua /opt/webmcp/ /opt/liquid_feedback_frontend/ main myconfig
    1.74 +<pre><code>su www-data -s $SHELL
    1.75 +/opt/moonbridge/moonbridge /opt/webmcp/bin/mcp.lua /opt/webmcp/ /opt/liquid_feedback_frontend/ main myconfig
    1.76  </code></pre>
    1.77  
    1.78  <p>In the latter case, the Moonbridge server will open a TCP port according to
    1.79  your configuration. Directly accessing this TCP port through your webbrowser
    1.80  is helpful for development purposes. For real-life deployment, however, it is
    1.81  recommended to further proxy the application (e.g. using nginx). The proxy can
    1.82 -also add HTTPS support (which is not supported by Moonbridge itself).</p>
    1.83 +also add HTTPS and/or HTTP/2 support (which is not supported by Moonbridge
    1.84 +itself).</p>
    1.85 +
    1.86 +<p>To start the Moonbridge as a background process, please refer to the Moonbridge
    1.87 +command line options:</p>
    1.88 +
    1.89 +<pre><code>Get this help message: moonbridge {-h|--help}
    1.90 +Usage: moonbridge \
    1.91 +           [-b|--background] \
    1.92 +           [-d|--debug] \
    1.93 +           [-f|--logfacility {DAEMON|USER|0|1|...|7}] \
    1.94 +           [-i|--logident &lt;syslog ident&gt; \
    1.95 +           [-l|--logfile &lt;logfile&gt;] \
    1.96 +           [-p|--pidfile &lt;pidfile&gt;] \
    1.97 +           [-s|--stats] \
    1.98 +           -- &lt;Lua script&gt; [&lt;cmdline options for Lua script&gt;]
    1.99 +</code></pre>
   1.100  </body>
   1.101  </html>

     2.1 --- a/INSTALL.mkd	Wed Apr 15 12:26:31 2015 +0200
     2.2 +++ b/INSTALL.mkd	Wed Apr 15 12:27:54 2015 +0200
     2.3 @@ -17,9 +17,10 @@
     2.4    * postgresql
     2.5    * libpq-dev
     2.6    * lighttpd (only for WebMCP 1.2.x support)
     2.7 +  * pmake or bmake (only for WebMCP 2.x with Moonbridge)
     2.8    * imagemagick
     2.9    * exim4
    2.10 -  * markdown2 (install with Python's pip)
    2.11 +  * markdown2 (``apt-get install python-pip; pip install markdown2``)
    2.12  
    2.13  If you're using any other Linux distribution or BSD system, install the
    2.14  necessary software components accordingly.
    2.15 @@ -33,14 +34,8 @@
    2.16  executing PostgreSQL's shell command `createuser` as database superuser
    2.17  (usually `pgsql`, or `postgres` for Debian installations):
    2.18  
    2.19 -    su - postgres
    2.20 -    createuser
    2.21 -
    2.22 -    Enter name of role to add: www-data
    2.23 -    Shall the new role be a superuser? (y/n) n
    2.24 -    Shall the new role be allowed to create databases? (y/n) y
    2.25 -    Shall the new role be allowed to create more new roles? (y/n) n
    2.26 -
    2.27 +    su postgres -s $SHELL
    2.28 +    createuser --no-superuser --createdb --no-createrole www-data
    2.29      exit
    2.30  
    2.31  
    2.32 @@ -59,7 +54,7 @@
    2.33      make
    2.34      mkdir /opt/liquid_feedback_core
    2.35      cp core.sql lf_update lf_update_issue_order /opt/liquid_feedback_core
    2.36 -    su - www-data
    2.37 +    su www-data -s $SHELL
    2.38      cd /opt/liquid_feedback_core
    2.39      createdb liquid_feedback
    2.40      createlang plpgsql liquid_feedback  # command may be omitted, depending on PostgreSQL version
    2.41 @@ -225,9 +220,9 @@
    2.42      echo "${PID}" > "${PIDFILE}"
    2.43  
    2.44      while true; do
    2.45 -      su - www-data -c 'nice /opt/liquid_feedback_core/lf_update dbname=liquid_feedback 2>&1 | logger -t "lf_updated"'
    2.46 -      su - www-data -c 'nice /opt/liquid_feedback_core/lf_update_issue_order dbname=liquid_feedback 2>&1 | logger -t "lf_updated"'
    2.47 -      su - www-data -c 'nice /opt/liquid_feedback_core/lf_update_suggestion_order dbname=liquid_feedback 2>&1 | logger -t "lf_updated"'
    2.48 +      su - www-data -s /bin/sh -c 'nice /opt/liquid_feedback_core/lf_update dbname=liquid_feedback 2>&1 | logger -t "lf_updated"'
    2.49 +      su - www-data -s /bin/sh -c 'nice /opt/liquid_feedback_core/lf_update_issue_order dbname=liquid_feedback 2>&1 | logger -t "lf_updated"'
    2.50 +      su - www-data -s /bin/sh -c 'nice /opt/liquid_feedback_core/lf_update_suggestion_order dbname=liquid_feedback 2>&1 | logger -t "lf_updated"'
    2.51        sleep 5
    2.52      done
    2.53  
    2.54 @@ -245,13 +240,13 @@
    2.55  `lf_update_suggestion_order`, the following commands should be executed in
    2.56  background:
    2.57  
    2.58 -    su - www-data
    2.59 +    su www-data -s $SHELL
    2.60      cd /opt/liquid_feedback_frontend/
    2.61      echo "Event:send_notifications_loop()" | ../webmcp/bin/webmcp_shell myconfig
    2.62  
    2.63  
    2.64 -12. Start the sytem
    2.65 --------------------
    2.66 +12. Start the system
    2.67 +--------------------
    2.68  
    2.69  After `lf_update` has been executed at least once and (in case of WebMCP 1.2.x)
    2.70  the webserver has been restarted (using the configuration above), you should be
    2.71 @@ -259,12 +254,28 @@
    2.72  
    2.73  If you use WebMCP 2.x, the server is started by calling:
    2.74  
    2.75 +    su www-data -s $SHELL
    2.76      /opt/moonbridge/moonbridge /opt/webmcp/bin/mcp.lua /opt/webmcp/ /opt/liquid_feedback_frontend/ main myconfig
    2.77  
    2.78  In the latter case, the Moonbridge server will open a TCP port according to
    2.79  your configuration. Directly accessing this TCP port through your webbrowser
    2.80  is helpful for development purposes. For real-life deployment, however, it is
    2.81  recommended to further proxy the application (e.g. using nginx). The proxy can
    2.82 -also add HTTPS support (which is not supported by Moonbridge itself).
    2.83 +also add HTTPS and/or HTTP/2 support (which is not supported by Moonbridge
    2.84 +itself).
    2.85 +
    2.86 +To start the Moonbridge as a background process, please refer to the Moonbridge
    2.87 +command line options:
    2.88 +
    2.89 +    Get this help message: moonbridge {-h|--help}
    2.90 +    Usage: moonbridge \
    2.91 +               [-b|--background] \
    2.92 +               [-d|--debug] \
    2.93 +               [-f|--logfacility {DAEMON|USER|0|1|...|7}] \
    2.94 +               [-i|--logident <syslog ident> \
    2.95 +               [-l|--logfile <logfile>] \
    2.96 +               [-p|--pidfile <pidfile>] \
    2.97 +               [-s|--stats] \
    2.98 +               -- <Lua script> [<cmdline options for Lua script>]
    2.99  
   2.100