Changed dbpath not reflected in Commandline?

[JonMikelV]

I shifted from a user to service based install and found that in the Commandline GUI under Advanced Options the dbpath was still pointing to the old location.

Should anything code wise be done about that or should users simply update it to point to the correct location (or does it matter at all)?

[kenkendk]

@JonMikelV

I shifted from a user to service based install and found that in the Commandline GUI under Advanced Options the dbpath was still pointing to the old location.

Should anything code wise be done about that or should users simply update it to point to the correct location (or does it matter at all)?

If we do something about that, maybe there should be a “migrate” or “move” tool. I think it would be strange to update these paths automatically. It does not really matter where the db’s are stored, but I can imagine it would be a surprise if the original user is removed and the files are gone.

Since you mention “Commandline GUI under Advanced Options”, I should mention that the value in “Advanced Options” is ignored:

Stuck on "Starting …"

Internally, the database path is stored in one place, and options in another. As many operations from the WebUI needs access to the database, it made sense to just hide the database things from the users. I have been planning to fix this a bit by adding some logic that checks if the user has changed the --dbpath option and ask them how to handle it, but for now it is a bit obscure. That really depends on how much data you put in there. It should not grow larger than the size of the database …

[JonMikelV]

@kenkendk

Since you mention “Commandline GUI under Advanced Options”, I should mention that the value in “Advanced Options” is ignored:

Yeah, I’ve been kind of noticing / assuming that many of the “Advanced Options” in the Commandline GUI are ignored. I assume SOME of them are used depending on what command is being executed otherwise why have them there in the first place. (I could including for reference purposes but then I’d assume they’d either be plain text, non-editable fields, or otherwise identified as “for reference”).