From 809c5355ef22caec5b83a4db6dccc7a355c2316f Mon Sep 17 00:00:00 2001
From: Philip <3460129+ppac@users.noreply.github.com>
Date: Sat, 22 Jul 2023 14:50:07 +0200
Subject: [PATCH 1/2] Update guide_vaultwarden.rst
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

data is stored in ´~/vaultwarden/data/´ instead of ´~/vaultwarden/output/data´
---
 source/guide_vaultwarden.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/source/guide_vaultwarden.rst b/source/guide_vaultwarden.rst
index cde6664f..eab4d4c7 100644
--- a/source/guide_vaultwarden.rst
+++ b/source/guide_vaultwarden.rst
@@ -190,8 +190,8 @@ You can create a backup of the database manually. ``cd`` to your project folder,
 
 .. code-block:: console
 
- [isabell@stardust ~]$ mkdir ~/vaultwarden/output/data/db-backup
- [isabell@stardust ~]$ sqlite3 ~/vaultwarden/output/data/db.sqlite3 ".backup '$HOME/vaultwarden/output/data/db-backup/backup.sqlite3'"
+ [isabell@stardust ~]$ mkdir ~/vaultwarden/data/db-backup
+ [isabell@stardust ~]$ sqlite3 ~/vaultwarden/data/db.sqlite3 ".backup '$HOME/vaultwarden/data/db-backup/backup.sqlite3'"
 
 .. note ::  You could run this command through a CRON job everyday - note that it will overwrite the same backup.sqlite3 file each time. If you want to save every version of the backup, please read further.
 
@@ -199,7 +199,7 @@ Alternatively, you can do the backup with a timestamp and it can be useful if yo
 
 .. code-block:: console
 
- [isabell@stardust ~]$ sqlite3 ~/vaultwarden/output/data/db.sqlite3 ".backup '$HOME/vaultwarden/output/data/db-backup/$(date +%Y-%m-%d).sqlite3'"
+ [isabell@stardust ~]$ sqlite3 ~/vaultwarden/data/db.sqlite3 ".backup '$HOME/vaultwarden/data/db-backup/$(date +%Y-%m-%d).sqlite3'"
 
 Restore up your vault manually
 ------------------------------

From 2dc70c4928582046f15da20d4fad7eb62644b80c Mon Sep 17 00:00:00 2001
From: Philip <3460129+ppac@users.noreply.github.com>
Date: Wed, 26 Jul 2023 17:48:05 +0200
Subject: [PATCH 2/2] Update guide_vaultwarden.rst

added some more information for the CRON job
---
 source/guide_vaultwarden.rst | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/source/guide_vaultwarden.rst b/source/guide_vaultwarden.rst
index eab4d4c7..0fa11389 100644
--- a/source/guide_vaultwarden.rst
+++ b/source/guide_vaultwarden.rst
@@ -201,6 +201,14 @@ Alternatively, you can do the backup with a timestamp and it can be useful if yo
 
  [isabell@stardust ~]$ sqlite3 ~/vaultwarden/data/db.sqlite3 ".backup '$HOME/vaultwarden/data/db-backup/$(date +%Y-%m-%d).sqlite3'"
 
+To do this, create a bash script with the last command and save it as ``~/backup-vaultwarden.sh`` and make it executable.
+
+.. code-block:: console
+
+ [isabell@stardust ~]$ chmod +x backup-vaultwarden.sh
+
+Now you can add this script into your crontab.
+
 Restore up your vault manually
 ------------------------------