Currently DiverCLI stores current db config in ~/.config/divercli/divercli.ini, but this could cause the user to mistakenly execute commands on the wrong database.
Seems better to have DiverCli look for configuration in the directory it is launched from, a bit like git or maven. In ~/.config/divercli/divercli.ini we can always keep global settings.
A directory setup for a H2 file DB could look like this (note DB could actually stay somewhere else):
Currently DiverCLI stores current db config in
~/.config/divercli/divercli.ini
, but this could cause the user to mistakenly execute commands on the wrong database.Seems better to have DiverCli look for configuration in the directory it is launched from, a bit like git or maven. In
~/.config/divercli/divercli.ini
we can always keep global settings.A directory setup for a H2 file DB could look like this (note DB could actually stay somewhere else):
Directories to connect to remote dbs like PostGRE instead might look like