Tilegarden is being used in https://github.com/azavea/pfb-network-connectivity, but since this will be the first production deployment and project integration, we've decided to copy it over and develop it there, to facilitate making the changes necessary for that project without too much overhead from trying to maintain compatibility with a hypothetical general implementation. The plan is to do what makes sense over there then bring that work back into Tilegarden proper as lessons learned and guidance for what makes sense in a general-purpose architecture.
To that end, this will be a running list of changes made over there that should (or should not) be considered for incorporation.
Tilegarden is being used in https://github.com/azavea/pfb-network-connectivity, but since this will be the first production deployment and project integration, we've decided to copy it over and develop it there, to facilitate making the changes necessary for that project without too much overhead from trying to maintain compatibility with a hypothetical general implementation. The plan is to do what makes sense over there then bring that work back into Tilegarden proper as lessons learned and guidance for what makes sense in a general-purpose architecture.
To that end, this will be a running list of changes made over there that should (or should not) be considered for incorporation.
Consider incorporating:
import
torequire
to be able to run in Node 8 without traspilation, remove Babel (see https://github.com/azavea/pfb-network-connectivity/commit/eb2dbe9c530a2b3d4c7fca02bcd112de87894c81)fs-promise
in favor of the built-inutil.promisify
(see https://github.com/azavea/pfb-network-connectivity/commit/19e94edc250c828bab669f18112b1c0648d71c15)claudia-local-api
Changes that are specific to PFB, not for incorporation:
DEV_
/PROD_
environment variable munging (might be worth refactoring, but the PFB change won't be directly applicable)