diff options
Diffstat (limited to 'docs/configuration.rst')
| -rw-r--r-- | docs/configuration.rst | 38 |
1 files changed, 20 insertions, 18 deletions
diff --git a/docs/configuration.rst b/docs/configuration.rst index 3aa34ac..e5870bb 100644 --- a/docs/configuration.rst +++ b/docs/configuration.rst @@ -11,7 +11,7 @@ Configuration This document presents the first steps to configure your Chimère. It has been updated for version 2.0.0. -Your session has to be initialised with these environment variables in +Your session has to be initialised with these environment variables in the Command Line Interface:: CHIMERE_PATH=/srv/chimere # change with your installation path @@ -32,7 +32,7 @@ To access these pages you have to identify with an account with *staff* and A *superuser* account is created at the initialization of the database. -Configuring the sites framework +Configuring the Sites framework ------------------------------- *Sites* framework allow you to serve the same content on different domains. @@ -57,25 +57,26 @@ An *Area* is the base of your map. It defines: user arriving on the map, * an order (to sort areas), * an availability, -* a default state. The /default/ area is viewed by default. Only one area can - be the default: activating this state disables it on the possible other area - with a default state, +* a "*default*" state. The "*default*" area is viewed by default. Only one area + can be the default: activating this state disables it on the possible other + area with a default state, * default checked categories (*not mandatory*), -* if categories are displayed dynamically (if dynamically is set, the end user +* if categories are displayed dynamically. If dynamically is set, the end user only views categories which have items on the map section he is currently - looking at), + looking at, * categories restriction (*not mandatory*): if no restriction is set all categories are available, * an external CSS file (*not mandatory*): an URL to an external CSS file, * restriction on the bounding box: if set to restricted, the end user can't pan - outside the defined bounding box. Due to technical reasons of OpenLayers, there - is at this time no restriction on the zoom, + outside the defined bounding box. Due to technical reasons of OpenLayers, + there is at this time no restriction on the zoom, * a map bounding box: this is the area to display when arriving on the map. If - the area is restricted it will be the bounding box that restricts the end user. - Hold the control key, click and drag to draw the bounding box, -* available layers (*not mandatory*; OSM Mapnik is used by default): OSM Mapnik - render, OSM MapQuest render, OSM Transport Map render, OSM CycleMap are - available by default. You can add new custom layers (cf. :ref:`managing-layers`). + the area is restricted it will be the bounding box that restricts the end + user. Hold the *control* key, click and drag to draw the bounding box, +* available layers (*not mandatory*: OSM Mapnik is used by default): OSM + Mapnik render, OSM MapQuest render, OSM Transport Map render, OSM CycleMap are + available by default. You can add new custom layers (cf. + :ref:`managing-layers`). *Areas* are customizable directly on the web administration interface in *Chimere > Areas*. @@ -103,8 +104,8 @@ password):: *Users* are customizable directly on the web administration interface in *Auth/User*. -To create a new account, simply click on the Add button near Users. Give a name -and a default password (the user can change it on his own later). +To create a new account, simply click on the *Add* button near *Users*. Give a +name and a default password (the user can change it on his own later). Then complete the other pieces of information. @@ -116,7 +117,8 @@ user must be trustworthy!). Otherwise you'll have to give permissions to this new user. It is easier not to add permission manually but to make this user a member of a group. -Two types of default group are proposed: application administrator and moderator. +Two types of default group are proposed: application administrator and +moderator. Moderator are limited to an *Area* (they only see items that are inside the bounding box). If a moderator manages many areas you'll have to select many @@ -125,7 +127,7 @@ groups. Detail of rights for default groups: +-----------------------------------------+-------------------------+---------------------------+-----------+ -| Task (add/modify/delete on) | Technical administrator | Application administrator | Moderator | +| Item (add/modify/delete on) | Technical administrator | Application administrator | Moderator | +=========================================+=========================+===========================+===========+ | User | yes | no | no | +-----------------------------------------+-------------------------+---------------------------+-----------+ |