updated to include backup infromation

This commit is contained in:
laxmanpradhan 2018-07-09 14:41:12 -07:00 committed by GitHub
parent b1d1926249
commit 3c662de4f2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -195,3 +195,27 @@ docker build -t bitwarden_rs .
## Building binary ## Building binary
For building binary outside the Docker environment and running it locally without docker, please see [build instructions](BUILD.md). For building binary outside the Docker environment and running it locally without docker, please see [build instructions](BUILD.md).
## Backup up your vault
1. the sqlite3 database
The sqlite3 database should be backed up using the proper sqlite3 backup command. This will ensure the database does not become corrupted if the backup happens during a database write.
```
sqlite3 /$DATA_FOLDER/db.sqlite3 ".backup '/$DATA_FOLDER/db-backup/backup.sq3'"
```
This command can be run via a CRON job everyday, however note that it will overwrite the same backup.sq3 file each time. This backup file should therefore be saved via incremental back either using a CRON job command that appends a timestamp or from another backup app such as Duplicati.
2. the key files
By default, these are located in the `$DATA_FOLDER` (by default /data in the docker). There are 3 files: rsa_key.der, rsa_key.pem, rsa_key.pub.der.
3. the attachements folder
By default, this is located in `$DATA_FOLDER/attachments`
4. Icon Cache
This is optional, the icon cache can redownload itself however if you have a large cache, it may take a long time. By default it is located in `$DATA_FOLDER/icon_cache`