Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Vaultwarden?
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.
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.
I have the same feelings about it. For now, the system does function very well.
It looks like there are 1900 forks on GitHub.
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.
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.