Expiry and diff support about vector-datasource HOT 5 CLOSED

We also fall into the group of providers that render the full planet, and then re-generate dirty tiles.

We don't have much in the way of documenting how all the services talk to each other, but we do have a vagrant image that should demonstrate how all the pieces fit together, in a purely local setting. I added some details to the vector-datasource wiki page you linked to, and the vagrant image repository can be found here:

https://github.com/mapzen/vagrant-tiles

from vector-datasource.

We do use osm2pgsql's tile expiry list. We can add that info to the docs.

from vector-datasource.

We also fall into the group of providers that render the full planet, and then re-generate dirty tiles

I thought tilestache didn't support "dirty" tiles and had no concept of serving old data that it knew to be outdated?

from vector-datasource.

Right - we are just using TileStache as the web server to generate the tiles. They are then stored in S3 + Fastly (in our install, could use other services in place of those), and the actual expiry and re-render process is handled outside of TileStache. @rmarianski will have more info :)

from vector-datasource.

Yup, that's correct. When osm2pgsql applies the update, we ask it to generate an expiry list, which we enqueue onto a work queue (sqs). That work is pulled off, and processed by a tool called tilequeue. That tool also handles enqueueing the work itself from the expiry list.

from vector-datasource.