The easiest way to generalize is just to get the list of all databases, then the list of all collections inside those databases.
In the long-run, though, it seems useful to allow for some flexibility here (e.g. if you don't care about repeats, or if your experiments are different enough that you only care about repeats in a particular project or experiment or iteration...)
So the slightly better, next-easiest thing to do is to offer a command-line flag or config option that disables database checking (instead of having to manually add a line to app.js)
Currently, we have the particular database to check hard-coded and also manually list out the collections.
The easiest way to generalize is just to get the list of all databases, then the list of all collections inside those databases.
In the long-run, though, it seems useful to allow for some flexibility here (e.g. if you don't care about repeats, or if your experiments are different enough that you only care about repeats in a particular project or experiment or iteration...)
So the slightly better, next-easiest thing to do is to offer a command-line flag or config option that disables database checking (instead of having to manually add a line to
app.js)