diff --git a/bitwarden_rs/readme.md b/bitwarden_rs/readme.md index e05707e..5e69d32 100644 --- a/bitwarden_rs/readme.md +++ b/bitwarden_rs/readme.md @@ -135,7 +135,6 @@ Password manager. RS version is simpler and lighter than the official bitwarden. ### Backup of just user data -For additional peace of mind, user-data daily export using the [official procedure.](https://github.com/dani-garcia/bitwarden_rs/wiki/Backing-up-your-vault)
For bitwarden_rs it means sqlite database dump and backing up `attachments` directory. The created backup files are overwriten on every run of the script, @@ -155,7 +154,7 @@ but borg backup is daily making snapshot of the entire directory. docker container exec bitwarden tar -czPf /data/BACKUP.attachments.tar.gz /data/attachments ``` - the script must be executabe - `chmod +x bitwarden-backup-script.sh` + the script must be **executabe** - `chmod +x bitwarden-backup-script.sh` * **cronjob** on the host
`crontab -e` - add new cron job
@@ -170,7 +169,7 @@ but borg backup is daily making snapshot of the entire directory. * let it run so it creates its file structure * down the container `docker-compose down` * in `bitwarden/bitwarden-data/`
- replace `db.sqlite3` with the one from the backup `BACKUP.bitwarden.db.sqlite3`
+ replace `db.sqlite3` with the backup one `BACKUP.bitwarden.db.sqlite3`
replace `attachments` directory with the one from the archive `BACKUP.attachments.tar.gz` * start the container `docker-compose up -d` diff --git a/bookstack/readme.md b/bookstack/readme.md index 62b1a51..570aa5e 100644 --- a/bookstack/readme.md +++ b/bookstack/readme.md @@ -180,7 +180,7 @@ but borg backup is daily making snapshot of the entire directory. docker container exec bookstack tar -czPf /config/BACKUP.bookstack.uploaded-files.tar.gz /config/www/ ``` - the script must be executabe - `chmod +x bookstack-backup-script.sh` + the script must be **executabe** - `chmod +x bookstack-backup-script.sh` * **cronjob** on the host
`crontab -e` - add new cron job
@@ -192,7 +192,7 @@ but borg backup is daily making snapshot of the entire directory. Assuming clean start, first restore the database before running the app container. * start only the database container: `docker-compose up -d bookstack_db` - * have `BACKUP.bookstack.database.sql` mounted in + * have `BACKUP.bookstack.database.sql` mounted in by placing it in `bookstack/bookstack-data` * exec in to the container and restore the database
`docker container exec -it bookstack_db /bin/bash`
`cd /config`