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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Maybe a silly question, but since I am considering making the jump to a password manager too, I am curious:
If I have a selfhosted server at home that is not connected to the public internet, can I still ise Keepass? Does it have to constantly sync with the server or is it enough that when I get home my passwords are syncing? Could that be a problem?
You have your local replica of the database on your device and once you're home or can connect to your home server (through VPN, for example) it will sync with the remote database. I used to have synthing running for this and it worked without issues.
If your server is not "online" you could vpn into your home network and use it that way. Another option is to have it local, meaning for example with bit/vault-warden you can still view your passwords if you don't have connection. But you can't edit or add new ones
I use KeePassXC, but am assuming KeePass is very similar.
You'll have a single file on your machine that is your encrypted password database. Syncing is not handled by KeePass and is your responsibility.
If you want to sync only when you get home, as long as your sync app that is fine with it, KeePass won't know or care.
Keep in mind if you make changes on two devices without keeping them in sync, one will probably get overwritten unless you take special care to handle it. (My sync app warns me, then I take both conflicting files and in the KeePass app, I can merge them to solve the conflict without data loss.)
Ideally keypass would allow handling such conflicts internally.
Thats the big disadvantage of a single-file approach.
Could easily be avoided e.g. sync whole folder and now you can have multiple files, e.g. 1 write file per program used.
I really like Strongbox on Mac for managing my Keepass-DBs. It is very well integrated and there even is a „no phoning home“ version that strictly runs locally.
and there even is a „no phoning home“ version that strictly runs locally.
Shouldn't that be all the versions?
Why would a password manager app that uses a local database need to phone home?
Maybe I expressed it a bit awkwardly. The other version has some integrations for syncing with Dropbox etc. and some third-party libraries. Strongbox zero is stripped of all of that.
Ok that makes more sense lol
Yeah, I've been wary of cloud based options so gone with KeePass and syncthing to leep things synced locally.