Skip to content
This repository has been archived by the owner on Jan 20, 2022. It is now read-only.

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

Open
williamflynt opened this issue Nov 11, 2019 · 2 comments

Comments

@williamflynt
Copy link

williamflynt commented Nov 11, 2019

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.

  • 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
Copy link
Contributor

missinglink commented Nov 15, 2019

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

@KristinaHus
Copy link

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants