Consider using rc over env for config

[olizilla]

The rc module allows the user to store the config for ipfs-deploy either in the current project, as env does, or in standard locations in ~ or /etc as per https://github.com/dominictarr/rc#standards

For things like account credentials, it'd be reasonable to store them in one place for all sites you use ipfs-deploy for, rather than in each project.

[agentofuser]

@olizilla is there a way to prevent rc from parsing command line arguments? It uses minimist to do that, which would conflict with our use of yargs.

Yargs allows reading configuration from an object with config() (https://yargs.js.org/docs/#api-configobject), so it could be passed the object resulting from rc files.

Yargs would then keep parsing cli arguments and generating the help text.

Yargs also has a feature I find adds familiarity to js devs which is to allow options to be configured within package.json, reducing the amount of dotfiles: https://yargs.js.org/docs/#api-pkgconfkey-cwd

It seems like we can have both by passing the rc object to config() and reading package.json with pkgConf().

Does this make sense?

[agentofuser]

There is also https://github.com/davidtheclark/cosmiconfig, which prettier uses. Seems nice!