Deployment
Local HTTP, the hosted Cloudflare Worker and its honest subsets, plus documentation site deployment.
Local HTTP
supercarto serve --port 8787
Full surface: maplets, SCR, transit, transit-route, health.
Cloudflare Worker
The compile path is Workers-compatible (fetch-based sources, no Node
built-ins), and cloud/worker/ packages it as a Cloudflare Worker: the same
/maplet, /scr, weather, daylight and terrain surface as the local HTTP
API, with per-IP rate limiting and ODbL attribution on every map response.
cloud/worker
src
wrangler.jsonc
README.md
It is deliberately a subset, stated on GET /:
- transit and traffic are not served — a Worker has no filesystem for a GTFS feed, and hosted mode ships no flow-provider keys
- the archive fallback (
protomapssource line) is coarse beyond z10-ish, and tile/feature fetches are capped so a request stays inside a Worker CPU budget - terrain answers
503rather than a rough answer: Terrarium tiles are PNG-encoded and the bundled zero-dependency decoder reads raw buffers only GET /healthzprobes Overpass only, so a 503 there means the Overpass leg is unreachable — not that the PMTiles fallback is down
Every hosted answer says what it cannot serve. An excerpt cannot mislead a model about what a full deployment would answer.