... | ... | @@ -47,7 +47,7 @@ In order to configure the settings-manager open and edit the |
|
|
* `AUTH_{{API}}_BASE` - base url of the authentication api
|
|
|
* `AUTH_{{API}}_TTL` - time to live of the token (in seconds)
|
|
|
* `AUTH_{{API}}_MIN_ROLE` - minimal role for authorized access (need to match one of the enumerated role in `AUTH_USER_ENUM_ROLES`)
|
|
|
* `DB_SINGLE_USE` - flag whether a single database is used for the widget-manager (all data models can be stored in a single database in different collections)
|
|
|
* `DB_SINGLE_USE` - flag whether a single database is used for the settings-manager (all data models can be stored in a single database in different collections)
|
|
|
* `DB_SINGLE_HOST` - host of the database
|
|
|
* `DB_SINGLE_PORT` - port of the database
|
|
|
* `DB_SINGLE_NAME` - name of the database
|
... | ... | @@ -86,11 +86,11 @@ AUTH_REST_TTL=86400 |
|
|
AUTH_REST_MIN_ROLE=Manager
|
|
|
|
|
|
# DB credentials
|
|
|
DB_ACTIVITY_HOST=localhost
|
|
|
DB_ACTIVITY_PORT=27017
|
|
|
DB_ACTIVITY_NAME=settings
|
|
|
DB_ACTIVITY_USER=settings
|
|
|
DB_ACTIVITY_PASS=manager
|
|
|
DB_SETTINGS_HOST=localhost
|
|
|
DB_SETTINGS_PORT=27017
|
|
|
DB_SETTINGS_NAME=settings
|
|
|
DB_SETTINGS_USER=settings
|
|
|
DB_SETTINGS_PASS=manager
|
|
|
```
|
|
|
|
|
|
# Run manager with:
|
... | ... | |