Ability to specify database location

[mraxilus]

It would be nice if I were able to specify the location of the database file to use, as I like to separate my work bookmarks from my personal ones.

Perhaps even a flag such as --database which would allow you to specify which database the command should deal with.

[jarun]

Why not use a tag, say... professional? If you ever need you can export specific tags too.

Coming to the option of specifying the DB location:
Switching databases is prone to human errors. Buku is written as a library. If you really want it you can do it at an API level. Check the classes:

class BukuDb
class BukuCrypt

I would like to keep Buku simple for the regular users.

[jarun]

I am re-opening this as I see more requests for this feature. You'll have it soon. :)

[jarun]

I am adding an undocumented API --db which should meet your requirement.

[dmarcoux]

Is there a reason to not document the --db flag?

[jarun]

Yes, we would like to keep it hidden from regular users. There's a high chance of mixing up if someone tries to use both.

[ChristopherA]

I like to use Boku with Tails OS, however, though I can now make the app be persistently installed using their new persistent apps feature, the DB file is saved by default to /home/amnesia/.local/buku/bookmarks.db when I want it saved to /home/amnesia/Persistent/.local/buku/bookmarks.db so that the database is persistent as well.

I can't recompile Boku to make this change — I have to use the scripted apt-get that Tails OS uses to make persistent apps function.

[jarun]

What's Boku?

You can use the --db flag. It's available but not documented.