17
submitted 9 months ago* (last edited 9 months ago) by anamethatisnt@lemmy.world to c/selfhosted@lemmy.world

I'm looking into different self hosted open source multiuser password safes and while there are many options I haven't found one with a .deb or .rpm install - only a whole bunch of docker compose.

Do you know of any good options that are included in debian 12 or fedora 39 repositories or at least that has a .deb or .rpm?

Currently I'm using keepassxc but been asked for something that either has a webui login for end users or an android app.

edit 2024-02-17:
After looking into the .deb and .rpm options available (passbolt or unofficial vaultwarden-deb) I decided to bite the bullet and install a debian 12 vm that I will try out different docker solutions on.

you are viewing a single comment's thread
view the rest of the comments
[-] wreckedcarzz@lemmy.world 2 points 9 months ago

Stupid q but why is the stop/start necessary? I'm running VW (and a dozen other things) thru docker on a synology dsm and it performs backups daily+monthly. Is it actually necessary to stop the container just to copy it?

[-] constantokra@lemmy.one 2 points 9 months ago

I've read that best practice is to do a database dump, in addition to backing up all the data files. It's my understanding that there's a slight chance of corrupting something in the database if you don't stop the service first, since something could be changed while you're doing your backup.

The easiest solution for me, as well as for being able to just restore my files and start the service again somewhere else, is to stop, backup, and restart. It's down for less than 5 minutes while i'm asleep. If I expected better uptime than that I wouldn't be trying to self host.

this post was submitted on 15 Feb 2024
17 points (94.7% liked)

Selfhosted

40347 readers
196 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS