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.
Easier for me to add a vm in my current system to handle backup, rollbacks and system updates. I’m much more confident that I can quickly restore a vm to new hardware f.e. Which feels important for a password vault.
Thanks a lot for the passbolt recommendation. Gonna look into it now!
FYI, if you run vaultwarden using docker compose with your data volume as a folder, all you have to do is bring it down for like 1minute, make a backup of the folders, and bring it back up. I use a cron script to do this nightly. When my vps host went out of business, I restored my docker folder to a new vps and was up and running again in a couple minutes. Also, you could easily restore it to a virtual machine, if you like. Docker with compose is extremely portable.
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?
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.
If you’re already using a VM anyway (especially for the backend/web UI piece) restoring the image won’t be any different for a server running docker vs one running apt packages.
True, I could use VM+Docker as you say. I’ve been thinking of making a dedicated “Docker VM” before when I’ve looked at interesting projects that has no other offerings.
I’ve felt that using docker in a vm robs docker of it’s advantages so why use it at all if I’m planning on having a vm? I guess one answer is “because the software you want is delivered as a docker image”.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
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:
selfh.st Newsletter and index of selfhosted software and apps
Easier for me to add a vm in my current system to handle backup, rollbacks and system updates. I’m much more confident that I can quickly restore a vm to new hardware f.e. Which feels important for a password vault.
Thanks a lot for the passbolt recommendation. Gonna look into it now!
FYI, if you run vaultwarden using docker compose with your data volume as a folder, all you have to do is bring it down for like 1minute, make a backup of the folders, and bring it back up. I use a cron script to do this nightly. When my vps host went out of business, I restored my docker folder to a new vps and was up and running again in a couple minutes. Also, you could easily restore it to a virtual machine, if you like. Docker with compose is extremely portable.
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?
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.
If you’re already using a VM anyway (especially for the backend/web UI piece) restoring the image won’t be any different for a server running docker vs one running apt packages.
True, I could use VM+Docker as you say. I’ve been thinking of making a dedicated “Docker VM” before when I’ve looked at interesting projects that has no other offerings.
I’ve felt that using docker in a vm robs docker of it’s advantages so why use it at all if I’m planning on having a vm? I guess one answer is “because the software you want is delivered as a docker image”.
It may seem like unnecessary overhead, but dockerized vaultwarden in a VM has been a huge improvement for me compared to unix-pass.
And with the volumes set up right, moving it is as easy as copy/pasting the folder it all lives in.
Sounds like I should get my docker vm. :)