TileStache.Goodies.ExternalConfigServer module

ExternalConfigServer is a replacement for WSGITileServer that uses external configuration fetched via HTTP to service all config requests.

Example usage, with gunicorn (http://gunicorn.org):

gunicorn –bind localhost:8888 “TileStache.Goodies.ExternalConfigServer:WSGIServer(url)”

class TileStache.Goodies.ExternalConfigServer.DynamicLayers(config, url_root, cache_responses, dirpath)

items()

keys()

parse_layer(layer_json)

class TileStache.Goodies.ExternalConfigServer.ExternalConfiguration(url_root, cache_dict, cache_responses, dirpath)

class TileStache.Goodies.ExternalConfigServer.WSGIServer(url_root, cache_responses=True, debug_level='DEBUG')

Bases: TileStache.WSGITileServer

Wrap WSGI application, passing it a custom configuration.

The WSGI application is an instance of TileStache:WSGITileServer.

This method is initiated with a url_root that contains the scheme, host, port and path that must prefix the API calls on our local server. Any valid http or https urls should work.

The cache_responses parameter tells TileStache to cache all responses from the configuration server.