I'm trying to set up an HTTP source that simultaneously saves any requested tile locally to an mbtiles db. I want to set up a persistent cache so that my tile service will be able to continue serving any tiles that have previously been requested when the original HTTP source becomes unreachable (and/or the service itself is restarted). I have the feeling that such a workflow is possible using existing tilelive modules, but maybe I'm overlooking something.
It looks like tilelive-cache just creates an in-memory cache. Do you think it would be useful to extend this to be able to use an arbitrary tilelive source as a cache? Or is what I'm describing already possible with other tilelive modules?
I'm trying to set up an HTTP source that simultaneously saves any requested tile locally to an mbtiles db. I want to set up a persistent cache so that my tile service will be able to continue serving any tiles that have previously been requested when the original HTTP source becomes unreachable (and/or the service itself is restarted). I have the feeling that such a workflow is possible using existing tilelive modules, but maybe I'm overlooking something.
It looks like
tilelive-cachejust creates an in-memory cache. Do you think it would be useful to extend this to be able to use an arbitrary tilelive source as a cache? Or is what I'm describing already possible with other tilelive modules?