Clarify where to specify data source addresses for non-Portland Metro builds

williamflynt commented 4 years ago

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 :sparkles:

A documented set of steps for downloading/hosting data and specifying the resource addresses to Helm.

Here's what I think could be improved :trophy:

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!

missinglink commented 4 years ago

[edit] got my wires crossed as to which repo this issue was on, so I've deleted my comments and moved them to https://github.com/pelias/docker/issues/142

KristinaHus commented 4 years ago

Hi, how can I add a pelias.json file to Kubernetes configurations?

pelias-deprecated / kubernetes

Clarify where to specify data source addresses for non-Portland Metro builds #114

Here's what I was expecting :sparkles:

Here's what I think could be improved :trophy: