Currently, clients and peers need each conversation file given individually as an argument. This is fine for now, but once we start to really scale, we can make the invocations a lot cleaner by allowing, e.g., *.toml as the argument, and have it do the right thing. For shadow experiments, this would also let us configure which conversation is on which client/peer by just moving the files, which is a lot simpler than doing that plus programmatically editing config files.
Currently, clients and peers need each conversation file given individually as an argument. This is fine for now, but once we start to really scale, we can make the invocations a lot cleaner by allowing, e.g., `*.toml` as the argument, and have it do the right thing. For shadow experiments, this would also let us configure which conversation is on which client/peer by just moving the files, which is a lot simpler than doing that plus programmatically editing config files.
Currently, clients and peers need each conversation file given individually as an argument. This is fine for now, but once we start to really scale, we can make the invocations a lot cleaner by allowing, e.g.,
*.tomlas the argument, and have it do the right thing. For shadow experiments, this would also let us configure which conversation is on which client/peer by just moving the files, which is a lot simpler than doing that plus programmatically editing config files.Fixed via
a08eda471f.