Hello there,
to test a library that calls into Riak, it would make sense to allow the library to start the locally-installed `riak` binary:
- on a different port than the default port, as to not interfere with a potentially running Riak cluster.
- using e.g. the `memory`-backend to make everything that is done ephemeral.
However, I have not found any way in Riak's documentation to customize the path that Riak reads its (basic) configuration file from: For binary installations this is `/etc/riak/riak.conf` and for source installations it is `../etc/riak.conf` (relative to the `riak` binary).
Because Riak takes these at start-up, and compiles a more advanced configuration as well as Erlang startup configuration (vm.args) in some way, it seems very difficult to manually pass in either a custom basic config or even a manually-made advanced configuration.
Is this currently possible? If so, how? (If not, I think it would make a great and probably not very complicated to create feature).
Thank you!
~Wiebe-Marten / Qqwy