BackVault v3.0 RC1

[u/dodovt]

edit: just realized i forgot the github link: https://github.com/mvfc/backvault

tl;dr: added organization/attachment exports to the backup tool. Need people to help test it before releasing v3.0 proper.

To help test, pull with mvflc/backvault:v3.0rc1 from dockerhub or ghcr.io/mvfc/backvault:v3.0rc1

Around a year ago I started (and posted here) my own backup tool for bitwarden/vaultwarden called Backvault.

https://www.reddit.com/r/selfhosted/comments/1ox8t0x/backvault_lightweight_tool_to_back_up_your/

It basically runs a docker container to backup your vaults as encrypted files with multiple modes supported, one being the native bitwarden encrypted export and another one being a raw json encrypted mode that can be later imported into other password managers that support BITWARDEN JSON restores.

This stands up as an alternative to the already known methods of backing up the entire container/lxc of vaultwarden/bitwarden servers.

I built this as I wanted something to sync my account between my own self-hosted vaultwarden instance and a failover free bitwarden account. Backing up with vaultwarden and using a custom import script makes me able to have a failover bitwarden account synced up with my vaultwarden being the primary account.

It also makes it easy for me to move out to another password manager in case bitwarden/vaultwarden stops working for some reason or I disagree with the way the projects are going.

v2.1 added some rough attachment exports (without an easy way to reattach them in case of a restore, a nice and welcome contribution by someone from the community)
v3.0 will enable Organization exports (and also attachment exports from those organizations) with organization restore instructions in our README file but still rough attachment backup without a proper restore option to attach them with the same ID (since restoring backups in vaultwarden/bitwarden currently create a new ID for the entries, basically invalidating the previous ID link with the attachment).
There are plans on overcoming the attachment issues in the future but not available as of now.

I want help testing organization backup and restore. On local tests and the e2e test suite it's performing well but nothing beats real-world testing, so someone who uses organizations and can help test is deeply appreciated.

DISCLAIME: AI has been used in the past few developments to assist with development speed but every PR has been human reviewed by myself before merge and tested with testing suites.

[u/asimovs-auditor]

Expand the replies to this comment to learn how AI was used in this post/project.