You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As discussed in pelias/wof-admin-lookup#288 (comment) we should consider better ways to publish the data generated by the code in this repository for easy use.
If we were to set up an NPM module for this repo, what would be the best way to publish it? Builds of this repo are probably too big for a CI job on TravisCI/CircleCI, but fairly inexpensive to run on a cloud VM instance.
Currently Geocode Earth is running regular builds, should we modify them to publish new NPM modules?
The text was updated successfully, but these errors were encountered:
As discussed in pelias/wof-admin-lookup#288 (comment) we should consider better ways to publish the data generated by the code in this repository for easy use.
Currently, we manually stuff the data deep in the https://github.com/pelias/wof-admin-lookup repo whenever we feel the need. This is certainly not ideal.
If we were to set up an NPM module for this repo, what would be the best way to publish it? Builds of this repo are probably too big for a CI job on TravisCI/CircleCI, but fairly inexpensive to run on a cloud VM instance.
Currently Geocode Earth is running regular builds, should we modify them to publish new NPM modules?
The text was updated successfully, but these errors were encountered: