Go to file
2012-10-05 15:57:30 +02:00
config Make logging format configurable (closes #4) 2012-10-05 15:52:51 +02:00
lib/cartodb Make logging format configurable (closes #4) 2012-10-05 15:52:51 +02:00
test Move more test support things under test/support 2012-10-05 15:57:30 +02:00
tools Fix iteration on redis keys 2012-09-21 12:58:34 +02:00
.gitignore Remove config files from repo, provide ./configure script to generate 2012-10-05 15:50:40 +02:00
app.js Require carto_data only after setting the global env (closes #28) 2012-07-10 09:49:56 +02:00
cluster.js Use cluster2 for clustering (see #33) 2012-09-28 13:05:49 +02:00
configure Add embedded informations about the configure script 2012-10-05 15:53:49 +02:00
LICENCE License is BSD (added file and reference) 2012-07-05 18:30:18 +02:00
Makefile Remove config files from repo, provide ./configure script to generate 2012-10-05 15:50:40 +02:00
NEWS.md 1.0.0 version 2012-10-03 16:39:21 +02:00
npm-shrinkwrap.json Update dependencies to have node-0.8 support 2012-09-28 13:04:32 +02:00
package.json fixed problem in cluster2 with pidfile name 2012-10-04 10:59:40 +02:00
README.md Add missing requirements (mapnik and postgis) 2012-10-05 15:56:20 +02:00
run_tests.sh Move more test support things under test/support 2012-10-05 15:57:30 +02:00

Windshaft-CartoDB

NOTE: requires node-0.8.x

This is the CartoDB map tiler. It extends Windshaft with some extra functionality and custom filters for authentication

  • reads dbname from subdomain and cartodb redis for pretty tile urls
  • configures windshaft to publish cartodb_id as the interactivity layer
  • gets the default geometry type from the cartodb redis store
  • allows tiles to be styled individually
  • provides a link to varnish high speed cache
  • provides a infowindow endpoint for windshaft
  • provides a map_metadata endpoint for windshaft

Requirements

[core]

  • node-0.6.x+
  • PostgreSQL-8.3+
  • PostGIS-1.5.0+
  • Redis 2.2.0+ (http://www.redis.io)
  • Mapnik 2.0 or 2.1

[for cache control]

Configure

Create the config/environments/.js files (there are .example files to start from). You can optionally use the ./configure script for this, see ./configure --help to see available options.

Look at lib/cartodb/server_options.js for more on config

Build/install

To fetch and build all node-based dependencies, run:

git clone
npm install

Note that the npm install step will populate the node_modules/ directory with modules, some of which being compiled on demand. If you happen to have startup errors you may need to force rebuilding those modules. At any time just wipe out the node_modules/ directory and run npm install again.

Run

node app.js <env> 

Where is the name of a configuration file under config/environments/.

Note that caches are kept in redis. If you're not seeing what you expect there may be out-of-sync records in there. Take a look: http://redis.io/commands

URLs

TILES

[GET] subdomain.cartodb.com/tiles/:table_name/:z/:x/:y.[png|png8|grid.json]

Args:

  • sql - plain SQL arguments
  • interactivity - specify the column to use in UTFGrid
  • cache_buster - if needed you can add a cachebuster to make sure you're rendering new
  • geom_type - override the cartodb default
  • style - override the default map style with Carto

STYLE

[GET/POST] subdomain.cartodb.com/tiles/:table_name/style

Args:

  • style - the style in CartoCSS you want to set

INFOWINDOW

[GET] subdomain.cartodb.com/tiles/:table_name/infowindow

Args:

  • infowindow - returns contents of infowindow from CartoDB.

MAP METADATA

[GET] subdomain.cartodb.com/tiles/:table_name/map_metadata

Args:

  • infowindow - returns contents of infowindow from CartoDB.

All GET requests are wrappable with JSONP using callback argument, including the UTFGrid map tile call.