liquid_feedback_core
changeset 380:0f5841ef67c6 v2.2.1
Updated README file to include information on lf_update_suggestion_order
author | jbe |
---|---|
date | Mon Mar 18 13:50:01 2013 +0100 (2013-03-18) |
parents | 54e2a6e63a94 |
children | fc1a491eb916 |
files | README |
line diff
1.1 --- a/README Mon Mar 18 11:40:53 2013 +0100 1.2 +++ b/README Mon Mar 18 13:50:01 2013 +0100 1.3 @@ -9,16 +9,23 @@ 1.4 Compile lf_update binary: 1.5 $ make 1.6 1.7 -Ensure that "lf_update dbname=liquid_feedback" is called regularly! 1.8 +Ensure that "lf_update dbname=liquid_feedback" and 1.9 +"lf_update_suggestion_order dbname=liquid_feedback" are called 1.10 +regularly! It is required to run these commands regularly 1.11 +(i.e. every 5 minutes via cron) to update cached supporter counts, 1.12 +to change the state of issues when neccessary, to calculate the 1.13 +result of votings, etc. If you wish, copy the created lf_update 1.14 +and lf_update_suggestion_order files to /usr/local/bin or a 1.15 +similar directory. 1.16 1.17 -It is required that lf_update is executed regulary (i.e. every 1.18 -5 minutes via cron) to update cached supporter counts, to change 1.19 -the state of issues when neccessary, and to calculate the result 1.20 -of votings. If you wish, copy the created lf_update file to 1.21 -/usr/local/bin or a similar directory. 1.22 +It is possible to run these two commands in parallel, if a setup 1.23 +requires splitting the load to multiple processor cores. In other 1.24 +cases it is recommended to run "lf_update" first, and then 1.25 +"lf_update_suggestion_order". 1.26 1.27 -On successful run, lf_update will not produce any output 1.28 -and exit with code 0. 1.29 +On successful run, these commands will not produce any output 1.30 +and exit with code 0. The command "lf_update_suggestion_order" may 1.31 +be called with a first argument of "-v" to print log output. 1.32 1.33 NOTE: When writing to the database, some INSERTs must be executed 1.34 within the same transaction, e.g. issues can't exist without