What format should we use for the RNode configuration file
Status | IN PROGRESS |
|---|---|
Stakeholders | Core development team dApp developers RNode operators |
Outcome | |
Due date | |
Owner | @Kelly Foster |
Background
The RNode software currently uses a TOML-formatted configuration file. There is a proposal to change to a HOCON-formatted configuration file https://rchain.atlassian.net/browse/CORE-1528.
Using this document
Please add feedback on the proposal to change from a TOML to a HOCON configuration file to comments in this document.
Action items
Comments
Please consider the following: Store the private key in the configuration file, but encrypted. So, the person starting the rnode needs to supply that decryption password on the command line or in a user prompt during startup. That way the private key is not "in the clear' anywhere. The IT operator shouldn't be able to steel funds from a different person putting up the stake.
Thanks for the comment, @Former user (Deleted). This is the plan. Please see https://rchain.atlassian.net/browse/CORE-1025 for details.
Unfortunately, this won't work in practice. Providing a password on the command-line is the same as providing the private key on the command-line. On the other hand, a user prompt is not suitable in a scripting environment, f.e. inside a docker image.
HOCON has some really nice properties: abstraction, static checking, termination, etc.
Yes, please!
I don't care what format you use, but please expose all options that can be passed in as commandline flags (it seems --has-faucet is not currently supported) and document how the file works. I'm willing to write the docs if someone prefers to socially explain it once.