-
-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hardcoded osm path #266
Comments
Sure thing, could you please open a pull request? The docker image should have the While you're there could you please fix the bash redirection code? It's |
We have adopted a convention over the years of using It seems that we always mount the config at So it's kind of just shifting the convention of using |
Yeah, this little script has always been a little confusing. One thing that's helpful is we do have a It's a bit messier than calling OSM_DATA_PATH=$(node -e "console.log(require('pelias-config').generate().imports.osm.datapath) );" Also note that the Polylines datapath is hardcoded in here several times, we might want to handle it the same way. |
hi
here de module
https://github.com/pelias/polylines/blob/master/docker_extract.sh#L9
it does not use the
pelias.json
configuration as it should but uses a hardcoded path,this breaks the operation in case the configuration is not the standard one
and however I think that the
pelias.json
file is the only place to read the pathsThe text was updated successfully, but these errors were encountered: