Differences

This shows you the differences between two versions of the page.

--- doc:appunti:linux:sa:liquidfeedback [2012/11/11 13:25] – [lf_update daemon] niccolo
+++ doc:appunti:linux:sa:liquidfeedback [2012/11/11 13:58] (current) – [LiquidFeedback administration] niccolo
@@ Line 183: / Line 183: @@
 </code>
-We must prepare a script that runs in an endless loop **''/usr/local/sbin/lf_updated''**:
+We must prepare a script that runs in an endless loop, **''/usr/local/sbin/lf_updated''**:
 <code bash>
@@ Line 213: / Line 213: @@
 </code>
-Then preare a script that start/stop the daemon **''/etc/init.d/lf_updated''**:
+Then preare a script that start/stop the daemon, **''/etc/init.d/lf_updated''**:
 <code bash>
@@ Line 308: / Line 308: @@
 insserv lf_updated
 </code>
+The daemon logs to syslog with the **''lf_updated''** tag.
 ===== Configuring Apache =====
@@ Line 411: / Line 413: @@
 FIXME Verify if this checklist is complete.
-  - Create another database.
+  - Create another **database**.
-  - Create another Apache VirtualHost and declare the configuration filename in **''WEBMCP_CONFIG_NAME''**.
+  - Create another **Apache VirtualHost** and declare the configuration filename in **''WEBMCP_CONFIG_NAME''**.
   - Create another config file in ''/usr/local/share/liquid_feedback_frontend/config/'' configuring at least **''absolute_base_url''** and **''database''** credentials.
+  - Add or update the **''lf_updated''** daemon to run on each database instance.
 ===== LiquidFeedback administration =====
-^ unit    | Administrators allow each user partecipate (or not) to the existing units.  |
+^ Eng     ^ Ita      ^ Note  ^
-^ area    | An unit can contain one or more areas. An user can partecipate to an area and he can delegate the entire area to someone else.  |
+^ unit    ^ sezione  | Administrators allow each user partecipate (or not) to the existing units.  |
-^ issue   |  |
+^ area    ^ area     | An unit can contain one or more areas. An user can partecipate to an area and he can delegate the entire area to someone else.  |
-^ policy  |  |
+^ issue   ^          |  |
+^ policy  ^          |  |
+An user with the admin right can login and click on the **//admin//** link.
+The first task for an administrator is to create some **units** containing some **areas**, where users can partecipate. From //Admin// -> //Units// -> //Create new unit// or //Edit areas//.
+Then the administrator create invite codes for new users. When creating a new user the admin define the login name (the identification), an email address, the admin right and the **units** where he can partecipate.
-An user with the admin right can login and click on the **//admin//** link. The first task for an administrator is to create invite codes for new users. When creating a new user the admin define the login name (the identification), an email address, the admin right and the **units** where he can partecipate.