liquid_feedback_core
view README @ 84:b0866d51b754
Backed out changesets dfa8e6a1f1e7, ca13b2614d10, and partly 0758a2e02620
- auto_support feature shall be added but implemented in a different way
- Delegating to non-active members shall be possible in database
- Incoming delegations MUST NOT be deleted when calling "delete_member"
- Index on "initiative"("issue_id") is not neccessary due to UNIQUE ("issue_id", "id") statement
- auto_support feature shall be added but implemented in a different way
- Delegating to non-active members shall be possible in database
- Incoming delegations MUST NOT be deleted when calling "delete_member"
- Index on "initiative"("issue_id") is not neccessary due to UNIQUE ("issue_id", "id") statement
| author | jbe |
|---|---|
| date | Sat Oct 16 23:56:35 2010 +0200 (2010-10-16) |
| 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