liquid_feedback_core
changeset 435:e3dd2c3629db
Added missing information on "lf_update_issue_order" to README file
author | jbe |
---|---|
date | Fri Jul 11 01:44:25 2014 +0200 (2014-07-11) |
parents | 692729de151a |
children | 34cc98defa8b |
files | README |
line diff
1.1 --- a/README Thu Jul 10 01:32:20 2014 +0200 1.2 +++ b/README Fri Jul 11 01:44:25 2014 +0200 1.3 @@ -9,7 +9,8 @@ 1.4 Compile lf_update binary: 1.5 $ make 1.6 1.7 -Ensure that "lf_update dbname=liquid_feedback" and 1.8 +Ensure that "lf_update dbname=liquid_feedback", 1.9 +"lf_update_issue_order dbname=liquid_feedback", and 1.10 "lf_update_suggestion_order dbname=liquid_feedback" are called 1.11 regularly! It is required to run these commands regularly 1.12 (i.e. every 5 minutes via cron) to update cached supporter counts, 1.13 @@ -21,11 +22,12 @@ 1.14 It is possible to run these two commands in parallel, if a setup 1.15 requires splitting the load to multiple processor cores. In other 1.16 cases it is recommended to run "lf_update" first, and then 1.17 -"lf_update_suggestion_order". 1.18 +"lf_update_issue_order" and "lf_update_suggestion_order". 1.19 1.20 On successful run, these commands will not produce any output 1.21 -and exit with code 0. The command "lf_update_suggestion_order" may 1.22 -be called with a first argument of "-v" to print log output. 1.23 +and exit with code 0. The commands "lf_update_issue_order" and 1.24 +"lf_update_suggestion_order" may be called with a first argument 1.25 +of "-v" to print log output. 1.26 1.27 NOTE: When writing to the database, some INSERTs must be executed 1.28 within the same transaction, e.g. issues can't exist without