Files
dataservices-api/server/extension
Mario de Frutos ac854a94af Fixed fallback to internal geocoder in nameplaces geocoding functions
- Fixed fallback becuase we have to use spiexceptions in this case
because we retrieve the configuration usig plpy.execute fuctions that
wrap any exception into a spiexception.

- In case we don't want to use Mapzen, we could leave the api_key empty
becuase we arise a ConfigException if the Mapzen api_key is empty so
we are able to make fallback. Right now we can't remove the mapzen
configuration because it'll fail when the InternalGeocoderConfig try to
load the ServiceDBConfig

This is a dirty hack, we should improve how the DB config is loaded. See
2017-05-26 12:41:41 +02:00
..
2016-07-11 10:51:16 +02:00

CARTO Data Services API server extension

Postgres extension for the CARTO Data Services API, server side.

Dependencies

This extension is thought to be used on top of CARTO geocoder extension, for the internal geocoder.

The following is a non-comprehensive list of dependencies:

  • Postgres 9.3+
  • Postgis extension
  • Schema triggers extension
  • cartodb-postgresql CARTO extension

Installation into the db cluster

This requires root privileges

sudo make all install

Execute tests

PGUSER=postgres make installcheck

Build, install & test

One-liner:

sudo PGUSER=postgres make all install installcheck

Install onto a CARTO user's database

Remember that is mandatory to install it on top of cdb_geocoder

psql -U postgres cartodb_dev_user_fe3b850a-01c0-48f9-8a26-a82f09e9b53f_db

and then:

CREATE EXTENSION cdb_dataservices_server;

The extension creation in the user's db requires superuser privileges.