I just feel uneasy about not knowing exactly where the database is and how to keep it safe. I thought that database just went poof if you logged out.
Comment on Self-hosted keypass fork recommendation
frongt@lemmy.zip 5 days ago
Vaultwarden?
You can write notes all day with no server at all. The server just Synchronizes it all.
Yes, that’s exactly how it works right now. Clients will keep a local copy of the database, so even if the server goes away for a while, you can still use it.
But you had the backup, you restored it, everything worked properly. I’m not sure what the issue is here.
altphoto@lemmy.today 5 days ago
frongt@lemmy.zip 5 days ago
It’s on your server, and whenever you keep your backup. I don’t know if it keeps a local copy on your phone when you log out or not. Generally I just don’t log out.
zikzak025@lemmy.world 5 days ago
Just don’t count on the current Bitwarden client being compatible with VaultWarden forever. Bitwarden’s new CEO is pushing to make more profit wherever possible, and recently rescinded the statement from the company’s website that the client would be free forever.
They’ll never be able to walk back the open source nature of the product, but they can choose to make their client incompatible with VaultWarden and push for the centrally hosted option as the only option.
Not sure if anyone’s forked the Bitwarden client yet, but that’s how I’d start using VaultWarden if the option exists.
Or, you know, skip the headache and just start using Keepass.
45o3b@lemmy.ml 4 days ago
It looks like there are 1900 forks on GitHub.
altphoto@lemmy.today 5 days ago
I have the same feelings about it. For now, the system does function very well.