Go to file
Sandro Santilli 6a2e0a338a Add versions for postgresql and cartodb requirements
This is because the CDB_QueryTables is used by the core: is provided
by CartoDB and only works with PostgreSQL 9.0+
2012-07-12 22:05:09 +02:00
app Block while connecting, fixing #37 2012-07-12 20:13:47 +02:00
config Run tests on "make check", using custom port for redis 2012-07-12 18:10:56 +02:00
logs updated gitignore and added required directories for node cluster to work out of the box 2011-09-05 17:01:23 +01:00
pids updated gitignore and added required directories for node cluster to work out of the box 2011-09-05 17:01:23 +01:00
test Enable psql test now that it doesn't hang anymore 2012-07-12 20:16:38 +02:00
websocket_test updated readme to reflect api key: 2012-06-01 21:19:02 +01:00
.gitignore updated gitignore and added required directories for node cluster to work out of the box 2011-09-05 17:01:23 +01:00
app.js quick tidy 2011-10-07 17:28:07 +01:00
cluster.js notes on cluster 2012-06-01 18:19:13 +01:00
LICENSE update licence 2011-10-07 17:19:37 +01:00
Makefile Run tests on "make check", using custom port for redis 2012-07-12 18:10:56 +02:00
package.json Run tests on "make check", using custom port for redis 2012-07-12 18:10:56 +02:00
README.md Add versions for postgresql and cartodb requirements 2012-07-12 22:05:09 +02:00

SQL API for cartodb.com

Provides a nodejs based API for running SQL queries against CartoDB.

  • Users are authenticated over OAuth or via an API KEY.
  • Authenticated requests to this API should always be made over SSL.

core requirements

  • postgres 9.0+
  • cartodb 0.9.5+ (for CDB_QueryTables)
  • redis
  • node >v0.4.8 && < 0.7.0>
  • npm

usage

Edit config/environments/.js Make sure redis is running and knows about active cartodb user.

node [cluster.js|app.js] <environment>

Supported values are developement, test, production

for examples of use, see /tests

Install dependencies

npm install

tests

see test/README.md

note on 0.4.x

output of large result sets is slow under node 0.4. Recommend running under 0.6 where possible.