Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support CLI options in the configuration file #12300

Open
eenagy opened this issue Nov 4, 2024 · 0 comments
Open

Support CLI options in the configuration file #12300

eenagy opened this issue Nov 4, 2024 · 0 comments
Labels
C-enhancement New feature or request S-needs-triage This issue needs to be labelled

Comments

@eenagy
Copy link
Contributor

eenagy commented Nov 4, 2024

Describe the feature

At the moment, reth offers limited support for configuration through a config file, meaning several important CLI options can’t be set there and must be entered each time on the command line. This can make the setup process a bit more cumbersome and limit the ability to share or update configurations across different environments. I’ve looked through the code but didn’t find support for including these options in the config file. Please let me know if I have overlooked something.

  • Many other execution clients allow all CLI options to be configured directly in a config file, simplifying sharing, maintaining consistency, and managing updates.

Additional context

I'm working on eth-nodes, a setup that launches any two clients and validators through packages, with each option mapped from debconf to generate the config file for each client. But since reth doesn't support all options directly in its config file, I had to wrap it in a bash script to pass the necessary CLI options. This workaround also meant adding an extra config file that isn't specific to reth, which isn't ideal. The goal is for all configs to work independently of eth-nodes packages and be usable on non-Debian systems without tweaks.

@eenagy eenagy added C-enhancement New feature or request S-needs-triage This issue needs to be labelled labels Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-enhancement New feature or request S-needs-triage This issue needs to be labelled
Projects
Status: Todo
Development

No branches or pull requests

1 participant