Entrypoint option in config_seeder.js about git2consul HOT 4 CLOSED

Yeah, I didn't consider the Docker use case when first designing git2consul. I can definitely see how that would cause a problem. I'll give this some thought, but I'm also happy to take patches.

from git2consul.

I can implement ENV solution without making breaking changes. So basically we can set global.endpoint to GIT2CONSUL_ENDPOINT if --entrypoint is not provided.

Otherwise ( adding --entrypoint into config_seeder.js ) I can't see a solution without making breaking changes.

from git2consul.

I could also really use this solution. I need to be able to override consul server IP. I am not savvy with npm nor javascript for that matter. I know that I have been able to make this work by manually updating the following two hardcoded references to localhost:

in lib/index.js:
global.endpoint = "127.0.0.1";

in node_modules/consul/lib/consul.js:
opts.host || '127.0.0.1'

I would like to be able to specify this thru either a parameter or an environment variable. I am sure this is probably pretty easy to do but at a loss for how to do it. I would have thought passing --host when running the node would work but it did not.

from git2consul.

This is available in 0.12.0 and up.

from git2consul.