You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
rn some settings can be configured via env vars (see dapp tools env vars, .dapprc)
to make migrating as painless as possible, there should be a forge config {init, migrate} command to create the default toml file or migrate from .dapprc (as much as possible, since .dapprc is a script, focus is on all key-value settings)
This will not be limited to critical settings, like endpoint etc, but should also provide a way to configure something like color output eventually.
Some settings, therefore are intended to apply globally. To support that we could support a global config file at ~/foundry.toml and one in a project as well, which "inherits" from that global one
This requires clear priorities for determining the final "Config":
global vars > repository config > global config
The text was updated successfully, but these errors were encountered:
Minor point that source .dapprc would need to happen outside of the migrate command, since it proved to be quite hard to run a shell script and get its outputs #190
rn some settings can be configured via env vars (see dapp tools env vars, .dapprc)
to make migrating as painless as possible, there should be a
forge config {init, migrate}
command to create the default toml file or migrate from .dapprc (as much as possible, since .dapprc is a script, focus is on all key-value settings)This will not be limited to critical settings, like endpoint etc, but should also provide a way to configure something like color output eventually.
Some settings, therefore are intended to apply globally. To support that we could support a global config file at
~/foundry.toml
and one in a project as well, which "inherits" from that global oneThis requires clear priorities for determining the final "Config":
global vars > repository config > global config
The text was updated successfully, but these errors were encountered: