liquid_feedback_core
view README @ 111:844c442c5a80
Work on new features; Slight change of behaviour regarding revocation of initiatives
New features:
- possiblity for members to store issue and voting comments
- initial work on notification system (new columns in table "membership" and new "event" table)
- added new type "issue_state" and new column "issue"."state"
Other changes:
- revocation of last initiative closes issue without delay, if issue has not been accepted yet
- moved table "contingent" up (after "system_setting" table)
New features:
- possiblity for members to store issue and voting comments
- initial work on notification system (new columns in table "membership" and new "event" table)
- added new type "issue_state" and new column "issue"."state"
Other changes:
- revocation of last initiative closes issue without delay, if issue has not been accepted yet
- moved table "contingent" up (after "system_setting" table)
| author | jbe |
|---|---|
| date | Thu Mar 03 00:01:37 2011 +0100 (2011-03-03) |
| parents | e6faf5ff83af |
| children | 92fc60ed705d |
line source
2 Setup the database:
3 $ createdb liquid_feedback
4 $ psql -v ON_ERROR_STOP=1 -f core.sql liquid_feedback
6 Optionally insert demo data:
7 $ psql -v ON_ERROR_STOP=1 -f demo.sql liquid_feedback
9 Compile lf_update binary:
10 $ make
12 If you wish, copy the created lf_update file to /usr/local/bin or a
13 similar directory. Ensure that "lf_update dbname=liquid_feedback"
14 is called regularly. On successful run, lf_update will not produce
15 any output and exit with code 0.
17 NOTE: When writing to the database, some INSERTs must be executed
18 within the same transaction, e.g. issues can't exist without
19 an initiative and vice versa.
21 To create an export file, which is containing all but private data,
22 you may use the lf_export shell-script:
23 $ lf_export liquid_feedback export.sql.gz
25 To uninstall the software, delete the lf_update binary
26 and drop the database by entering the following command:
27 $ dropdb liquid_feedback