-
Notifications
You must be signed in to change notification settings - Fork 679
Accept CLI args via config file #1041
Comments
Agreed. |
More esoteric things could go in the config file, though I'd like to include as many command line options as possible - I hate having to create a configuration file for one off configurations because the command line option isn't available. Would be nice to have good usage output as well (we should use |
helpeth uses Complex conditions are painful:
|
+1 for having a configuration file... created a concept branch for one - takes config from cmd line and merges it over |
Would accept a PR for this if it were effectively generating the config file parsing from the command line arg spec, and allowed command line args to override options specified in the config file. Not likely to prioritize this feature in the near future, however. |
This will be addressed in #811 |
Splitting off from trufflesuite/ganache-cli-archive#24.
As suggested in https://github.com/ethereumjs/testrpc/issues/23 parsing a
genesis.json
would be a useful feature and in #24 we discussed perhaps it is better to have a separate configuration file and/or commandline parameters (for a subset or all options).Given there are two other PRs in the pipeline (trufflesuite/ganache-cli-archive#28 (gasLimit) and trufflesuite/ganache-cli-archive#36 (gasPrice)) as well as the
--seed
and perhaps lightwallet options, I think it would be useful to discuss and make a decision on how configuration should work.I would vote for having a comprehensive configuration file and including some frequently used options in the commandline.
The text was updated successfully, but these errors were encountered: