Rippled: Validator token file

[nbougalis]

It should be possible to keep the validator's token in a separate file, and to load it indirectly by referencing the file path in the primary configuration. Additionally, it should be possible to specify the path to the token file via a command-line argument --validator-token.

[movitto]

:+1: love the concept of seperate config's for separate things, would make it easier to tailor different config settings from different tools / environments. Any ideas on implementation details? There are a few different solutions from what I've seen. Something like httpd would entail a generic 'include' or 'require' statement which is used to pull in same-syntax config files from generic locations on the filesystem (including directory globbing so that specific configs don't need to be listed in rippled.cfg). Other services have specialized configs (for ex pg_hba.conf in postgresql) which have their own syntax but can be custom tailored / optimized for their purposes.

[nbougalis]

I'd be OK with some kind of include and or import statement. For example, the following stanza could load the files /path/to/file/a and /data/is/cool:

[include]
/path/to/file/a
/data/is/cool

We are also thinking about improving the config file format more generally, perhaps going so far as to migrate to a format like TOML. We should see what support is available for including/referencing other files.

[movitto]

I'd be OK with some kind of include and or import statement. For example, the following stanza could load the files /path/to/file/a and /data/is/cool:

Awesome! Any thoughts on globbing and/or having a directory that's included in the default config file? (eg. /etc/opt/ripple/cfg.d)

We are also thinking about improving the config file format more generally, perhaps going so far as to migrate to a format like TOML. We should see what support is available for including/referencing other files.

Not too familiar w/ TOML but seems concise, will check it out!