# HG changeset patch # User bsw # Date 1429093674 -7200 # Node ID e0a6eabedd16ac2b69eb5b4f498916e3a9f8083d # Parent f981928d1984f4dcd3c73256a78285c30697cefe# Parent bf158c59f827c762731e7af5cc26f05c457785d7 merge diff -r f981928d1984 -r e0a6eabedd16 INSTALL.html --- a/INSTALL.html Wed Apr 15 12:26:31 2015 +0200 +++ b/INSTALL.html Wed Apr 15 12:27:54 2015 +0200 @@ -20,9 +20,10 @@
apt-get install python-pip; pip install markdown2
)If you're using any other Linux distribution or BSD system, install the
@@ -35,14 +36,8 @@
executing PostgreSQL's shell command createuser
as database superuser
(usually pgsql
, or postgres
for Debian installations):
su - postgres
-createuser
-
-Enter name of role to add: www-data
-Shall the new role be a superuser? (y/n) n
-Shall the new role be allowed to create databases? (y/n) y
-Shall the new role be allowed to create more new roles? (y/n) n
-
+su postgres -s $SHELL
+createuser --no-superuser --createdb --no-createrole www-data
exit
@@ -60,7 +55,7 @@
make
mkdir /opt/liquid_feedback_core
cp core.sql lf_update lf_update_issue_order /opt/liquid_feedback_core
-su - www-data
+su www-data -s $SHELL
cd /opt/liquid_feedback_core
createdb liquid_feedback
createlang plpgsql liquid_feedback # command may be omitted, depending on PostgreSQL version
@@ -225,9 +220,9 @@
echo "${PID}" > "${PIDFILE}"
while true; do
- su - www-data -c 'nice /opt/liquid_feedback_core/lf_update dbname=liquid_feedback 2>&1 | logger -t "lf_updated"'
- su - www-data -c 'nice /opt/liquid_feedback_core/lf_update_issue_order dbname=liquid_feedback 2>&1 | logger -t "lf_updated"'
- su - www-data -c 'nice /opt/liquid_feedback_core/lf_update_suggestion_order dbname=liquid_feedback 2>&1 | logger -t "lf_updated"'
+ su - www-data -s /bin/sh -c 'nice /opt/liquid_feedback_core/lf_update dbname=liquid_feedback 2>&1 | logger -t "lf_updated"'
+ 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"'
+ 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"'
sleep 5
done
@@ -245,12 +240,12 @@
lf_update_suggestion_order
, the following commands should be executed in
background:
-su - www-data
+su www-data -s $SHELL
cd /opt/liquid_feedback_frontend/
echo "Event:send_notifications_loop()" | ../webmcp/bin/webmcp_shell myconfig
-12. Start the sytem
+12. Start the 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
@@ -258,13 +253,30 @@
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
+su www-data -s $SHELL
+/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).
+also add HTTPS and/or HTTP/2 support (which is not supported by Moonbridge
+itself).
+
+To start the Moonbridge as a background process, please refer to the Moonbridge
+command line options:
+
+Get this help message: moonbridge {-h|--help}
+Usage: moonbridge \
+ [-b|--background] \
+ [-d|--debug] \
+ [-f|--logfacility {DAEMON|USER|0|1|...|7}] \
+ [-i|--logident <syslog ident> \
+ [-l|--logfile <logfile>] \
+ [-p|--pidfile <pidfile>] \
+ [-s|--stats] \
+ -- <Lua script> [<cmdline options for Lua script>]
+