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
The biggest issue is that the configuration and the systemd unit file is in the same file, making it more harder for administrators to change the config. It would be great to be able to ship a systemd unit file that allows updating the package to also reload the service, while keeping the configuration unchanged.
I have tried to make it better by loading the arguments from EnvironmentFile, but I feel it is only a hack for now:
the big caveat here is that mev-boost has seen a lot more production usage although I run mev-boost-rs in many of my testnet setups and haven't had any issue to date. you could try running mev-boost-rs in your testnet/staging environments and if you gain confidence then try mainnet
also happy to provide support if you run into any issues along the way
I have made RPM package for MEV-Boost that is hosted currently at https://copr.fedorainfracloud.org/coprs/jonny/Ethereum/
The source for the SPEC files used to build the RPM can be found here:
https://github.com/hegjon/mev-boost-rpm
The biggest issue is that the configuration and the systemd unit file is in the same file, making it more harder for administrators to change the config. It would be great to be able to ship a systemd unit file that allows updating the package to also reload the service, while keeping the configuration unchanged.
I have tried to make it better by loading the arguments from EnvironmentFile, but I feel it is only a hack for now:
mev-boost@.service
And the environment file for mainnet:
The text was updated successfully, but these errors were encountered: