chore: configuration file #129
Assignees
Labels
enhancement
New feature or request
Comments
mfw78
added a commit
that referenced
this issue
Jan 18, 2024
# Description Configuration methodology (via CLI options) has been outgrown with the number of options. This PR removes all chain / network related configuration and moves to a configuration file. # Changes - [x] Move all configuration for chains to a dedicated file - [x] Remove unused features (replay tx / replay block) - [x] Eliminates dynamic download of filter policies (now within configuration file) - [x] Update `README.md` ## How to test 1. Adjust the `config.json.example` for suitable configuration 2. Run and verify sync process completes warmup ## Related Issues Fixes #129 --------- Co-authored-by: Leandro <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background
It is frustrating, and error prone to get the configuration for the watch-tower correct given the index-specific configuration.
Details
All network CLI options should be removed and replaced with a mandatory configuration file config option. This should allow multiple networks to be configured so that users may run a sovereign watch-tower.
Acceptance criteria
The text was updated successfully, but these errors were encountered: