cartodb4/dataservices-api
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Updated the User database configuration section

Browse Source
This commit is contained in:
Antonio 2017-08-11 10:21:10 +02:00
parent 0cd0087f3f
commit 797a2dbd24
1 changed files with 27 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
README.md
View File

@ -92,7 +92,7 @@ Steps to deploy a new Data Services API version :
``` ```
- Give permission to execute and select to the `dataservices_user` user: - Give permission to execute and select to the `dataservices_user` user:
``` ```
psql -U postgres -d dataservices_db -c "BEGIN;CREATE EXTENSION IF NOT EXISTS observatory; COMMIT" -e psql -U postgres -d dataservices_db -c "BEGIN;CREATE EXTENSION IF NOT EXISTS observatory version 'dev'; COMMIT" -e
psql -U postgres -d dataservices_db -c "BEGIN;GRANT SELECT ON ALL TABLES IN SCHEMA cdb_observatory TO dataservices_user; COMMIT" -e psql -U postgres -d dataservices_db -c "BEGIN;GRANT SELECT ON ALL TABLES IN SCHEMA cdb_observatory TO dataservices_user; COMMIT" -e
psql -U postgres -d dataservices_db -c "BEGIN;GRANT EXECUTE ON ALL FUNCTIONS IN SCHEMA cdb_observatory TO dataservices_user; COMMIT" -e psql -U postgres -d dataservices_db -c "BEGIN;GRANT EXECUTE ON ALL FUNCTIONS IN SCHEMA cdb_observatory TO dataservices_user; COMMIT" -e
psql -U postgres -d dataservices_db -c "BEGIN;GRANT SELECT ON ALL TABLES IN SCHEMA observatory TO dataservices_user; COMMIT" -e psql -U postgres -d dataservices_db -c "BEGIN;GRANT SELECT ON ALL TABLES IN SCHEMA observatory TO dataservices_user; COMMIT" -e
@ -254,14 +254,16 @@ jsonb_set(
``` ```
### User database configuration ### User database configuration
#### Option 1
User (client) databases need also some configuration so that the client extension can access the server: User (client) databases need also some configuration so that the client extension can access the server:
#### Users/Organizations ##### Users/Organizations
```sql ```sql
SELECT CDB_Conf_SetConf('user_config', '{"is_organization": false, "entity_name": "<YOUR_USERNAME>"}'); SELECT CDB_Conf_SetConf('user_config', '{"is_organization": false, "entity_name": "<YOUR_USERNAME>"}');
``` ```
#### Dataservices server ##### Dataservices server
The `geocoder_server_config` (the name is not accurate for historical reasons) entry points The `geocoder_server_config` (the name is not accurate for historical reasons) entry points
to the dataservices server DB (you can use a specific database for the server or your same user's): to the dataservices server DB (you can use a specific database for the server or your same user's):
@ -272,10 +274,31 @@ SELECT CDB_Conf_SetConf(
'{ "connection_str": "host=localhost port=5432 dbname=<SERVER_DB_NAME> user=postgres"}' '{ "connection_str": "host=localhost port=5432 dbname=<SERVER_DB_NAME> user=postgres"}'
); );
``` ```
#### Search path ##### Search path
The search path must be configured in order to be able to execute the functions without using the schema: The search path must be configured in order to be able to execute the functions without using the schema:
```sql ```sql
ALTER ROLE "<USER_ROLE>" SET search_path="$user", public, cartodb, cdb_dataservices_client; ALTER ROLE "<USER_ROLE>" SET search_path="$user", public, cartodb, cdb_dataservices_client;
``` ```
#### Option 2
Add the following entry to the `geocoder` entry of the `cartodb/config/app_config.yml` file:
```
api:
host: 'localhost'
port: '5432'
user: 'dataservices_user'
dbname: 'dataservices_db'
```
In the `cartodb/config/app_config.yml` file, enable the desired dataservices:
```
enabled:
geocoder_internal: false
hires_geocoder: false
isolines: false
routing: false
data_observatory: true
```