VaultWarden backup:#148
Open
Vetal-ca wants to merge 1 commit into
Open
Conversation
Vetal-ca
force-pushed
the
feature/backup1
branch
2 times, most recently
from
2973df4 to
5a76980
Compare
|
+1 Would've loved this before I tried out rolling my own backup procedures |
Vetal-ca
force-pushed
the
feature/backup1
branch
from
5a76980 to
7828a03
Compare
- Helm chart updated - Restore script - Documentation
Vetal-ca
force-pushed
the
feature/backup1
branch
from
7828a03 to
8321a45
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added optional backup sidecar(s), based on https://github.com/ttionya/vaultwarden-backup
Can be used on local SQLite storage