mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[PR #6028] [CLOSED] docs(readme): add reference to data backup documentation #3706
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#3706
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/dani-garcia/vaultwarden/pull/6028
Author: @rudra-singh1
Created: 7/4/2025
Status: ❌ Closed
Base:
main← Head:main📝 Commits (1)
b5454e8docs(readme): add reference to data backup documentation📊 Changes
2 files changed (+129 additions, -0 deletions)
View changed files
📝
README.md(+2 -0)➕
resources/data-backup.md(+127 -0)📄 Description
this pr adds a new data backup documentation in the "resources" folder, detailing backup and restore processes for vaultwarden, including automated scripts for backups and cleanup. a reference to this documentation is added under the "Usage" section in the main README.md. addresses partially the database migration point mentioned in: https://github.com/dani-garcia/vaultwarden/issues/246 . i believe in the future this documentation can be updated to support those different databases, but for now, a basic data backup walk thru is important
why this pr Is needed: vaultwarden users need reliable backup solutions to prevent data loss, enable disaster recovery, and support migrations. many community networks have asked my team how we add backup capabilities to vaultwarden. i thought it'd be easier to put this information out here instead, for ease of access to everyone.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.