On 08/06/15 11:38, Andrew Stuart wrote:
You can currently, for testing purposes, hardcode a config file directly into that C file
in the aptly-named "hardcoded_jsoncfg[]" so you don't essentially have to worry
about anything else.
OK I can see that in the code. Where should I look to find what options I can
put into the config file and how I should structure it (presumably JSON of
course but I assume essentially key/value pairs - anyway if there’s an example
I can copy)?
Config files are generated by rumprun. You can dump them with rumprun
-D or save them with rumprun -T. (I thought we already had that
discussion a few weeks ago?)
