config files: what're they for?

[phritz]

No description provided.

[phritz]

OK, talked to why about this and (briefly) I think we agree that:

• things that affect server behavior should have artifacts (eg, config files).
• server config should be concentrated in the fewest different types of mechanisms possible. For example if we have config files don't also smear config across command line flags and and rpc to fetch state from a config server
• we like config files, favor them over command line flags in general
• there will be config that doesn't change over the lifetime of the server and config that can (eg, a miner's ask strategy). put these things in separate files.
• reload reloadable config in response to explicit action (cmd for example)

[whyrusleeping]

One caveat I'd like to note, I think that command line flags to the daemon process that override certain behaviours is fine. For example, the --offline flag on go-ipfs. Sometimes I want to temporarily run my daemon without networking.

[dignifiedquire]

Sounds good to me