IPFS_BOOTSTRAP / env-override of config?

[jbenet]

As noted in #250, it would be nice to be able to pass in bootstrap addresses as part of an envvar or a cli param. This would make it easier to programmatically create nodes.

What might make sense is to design a seamless way for env vars to override configuration variables, that way we dont have to create multiple ways of changing them.

Maybe a IPFS_CONFIG(_Key)+ ->config(.Key)+ approach. (e.g.IPFS_Config_Bootstrap)... hmm i dont like this.

[whyrusleeping]

Thats tricky to work out in a way that makes sense....

[btc]

@whyrusleeping What challenges do you see?

I don't know of any concrete use cases for other config values. I just know that env bootstrapping is important for Docker.

docker run -e "IPFS_BOOTSTRAP=10.10.10.10" -d go-ipfs

[jbenet]

i think he means my general suggestion

[btc]

Not sure we need to worry about the general case just yet. At least not until a) the pipeline clears up a bit or b) a use case arises that shows importance of a general solution.

[jbenet]

fair enough

[daviddias]

We can keep it simple by using env vars and giving the option to extend the default config with --config= option

[hannahhoward]

@gmasgras can you comment on whether this is still relevant based on the Docker-izing work you are doing? Should it remain open?

[gmasgras]

Here is a PR that addresses this issue: #6325

[lidel]

Continued in #387