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
{{ message }}
This repository has been archived by the owner on Jan 20, 2022. It is now read-only.
I was trying to understand how to build a USA-only instance of Pelias and I noticed there is a lack of "direction" on how to specify data sources.
Here's what I was expecting ✨
A documented set of steps for downloading/hosting data and specifying the resource addresses to Helm.
Here's what I think could be improved 🏆
I can think of a few solutions to this problem. An experienced contributor's opinion on best practices for the Pelias ecosystem would be appreciated.
Clear documentation on what to change for your specific build, using the existing templates.
A separate object in the values.yaml files containing clearly defined dataSources.
A separate data-sources.yaml that's imported to the templates.
It would really help to get input on this, as I'm still not clear on what needs changed to specify custom data repositories. I'm happy to implement and submit the PR!
The text was updated successfully, but these errors were encountered:
Hey team!
I was trying to understand how to build a USA-only instance of Pelias and I noticed there is a lack of "direction" on how to specify data sources.
Here's what I was expecting ✨
A documented set of steps for downloading/hosting data and specifying the resource addresses to Helm.
Here's what I think could be improved 🏆
I can think of a few solutions to this problem. An experienced contributor's opinion on best practices for the Pelias ecosystem would be appreciated.
values.yaml
files containing clearly defineddataSources
.data-sources.yaml
that's imported to the templates.It would really help to get input on this, as I'm still not clear on what needs changed to specify custom data repositories. I'm happy to implement and submit the PR!
The text was updated successfully, but these errors were encountered: