I wished it was easier to set hostname of ES... about config HOT 4 CLOSED

@rjpereira in production we have static DNS addresses for our AWS load balancers in each environment, then those DNS names are stored in a per-stack pelias.json file which is loaded via env var as per https://github.com/pelias/config#production-settings

from config.

I would prefer not to change the existing implementation of pelias/config to one that supported fallback scenarios as that would add complexity that IMHO could be better handled by the system administrator via scripts.

from config.

I'm not sure I fully understand, so if I'm way off, let me know.

From what I gather you have an environment with hard dependencies between your service layer and your application layer, presumably the services will have to expose their location to the application somehow.

Am I correct in saying that the issue is converting that service discovery info in to JSON format?

from config.

Hello from over a year in the future.

Since this issue was first opened Pelias has moved towards having many services, so the question of how to configure them has only grown in importance. However I agree with missinglink that we don't intend to support ENV vars for configuring the hosts. We like pelias.json. Without it, there would be far too many ENV vars to configure.

Instead, here are some suggestions. that might be useful by themselves or in combination:

• Use DNS to provide consistent hostnames for Pelias to use across services
• Use a load balancer so that needing to change the hostname happens less often
• Use some mechanism to update pelias.json and restart any API instances when it changes. This is useful anyways for pushing config changes

For geocode.earth we use that last system, using the Kubernetes ConfigMap feature, and tell Kubernetes to re-create our API containers whenever the config changes.

If anyone is stuck figuring out a good way to handle this, let us know, we can probably help.

from config.