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
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.
The text was updated successfully, but these errors were encountered:
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.
Additional context
I'm working on
eth-nodes
, a setup that launches any two clients and validators through packages, with each option mapped fromdebconf
to generate the config file for each client. But sincereth
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 toreth
, which isn't ideal. The goal is for all configs to work independently ofeth-nodes
packages and be usable on non-Debian systems without tweaks.The text was updated successfully, but these errors were encountered: