Docs - Docker - add backups dir volume

Author: SimonMellerin

docs/content/backup_restore.md

@@ -8,10 +8,10 @@ but also a tiny backups manager which handle backup files for you.
 The backup command will use the [predefined or configured binary](./configuration/basics#binaries) for your
 database vendor with correct parameters to dump your database.
 
-Each time you launch the backup command, [a backup file is stored in a directory](./configuration/basics#storage-directory) (See
+Each time you launch the backup command, [a backup file is stored in a directory](./configuration/basics#storage) (See
 [Storage section](#storage) below for more information on how backup files are stored).
 
-With time, this directory will grow, that's why a [backup expiration age](./configuration/basics#storage-directory#backup-expiration-age)
+With time, this directory will grow, that's why a [backup expiration age](./configuration/basics#backup-expiration-age)
 was added. Every time you launch the command, at the end, it will be asked if you want to remove obsolete
 backup files (i.e. files that have passed their expiration date).
 
@@ -337,13 +337,18 @@ docker compose run dbtools restore --ignore-default-options
 As mentioned earlier on this page, *DbToolsBundle* can list existing backup files
 when you want to restore a previous one with the restore command.
 
-All backups are stored in a directory. By default this directory is <span db-tools-flavor="standalone-docker">`./var/db_tools` (relative to the yaml config file)</span><span db-tools-flavor="symfony">`%kernel.project_dir%/var/db_tools`</span>
-but [you can choose the directory you want](./configuration/basics#storage-directory).
+All backups are stored in a directory. By default this directory is
+<span db-tools-flavor="standalone">`./var/db_tools` (relative to the yaml config file)</span>
+<span db-tools-flavor="symfony">`%kernel.project_dir%/var/db_tools`</span>
+<span db-tools-flavor="docker">`/var/www/var/db_tools` (inside the docker container)</span>
+but [you can choose the directory you want](./configuration/basics#storage).
 
 In this directory, each backup is put in sub-directories depending on the backup date. The backup's filename
 is generated from the backup date and the DBAL connection name of the database.
 
 For a backup made the 2023-05-15 at 12:22:35 for the default connection, the filename will be :
-<span db-tools-flavor="standalone-docker">`./var/db_tools/2023/05/default-20230515122235.sql`</span><span db-tools-flavor="symfony">`%kernel.project_dir%/var/db_tools/2023/05/default-20230515122235.sql`</span>.
+<span db-tools-flavor="standalone">`./var/db_tools/2023/05/default-20230515122235.sql`</span>
+<span db-tools-flavor="symfony">`%kernel.project_dir%/var/db_tools/2023/05/default-20230515122235.sql`</span>
+<span db-tools-flavor="docker">`/var/www/var/db_tools/2023/05/default-20230515122235.sql`</span>.
 
 Note that the file extension may vary depending on the database vendor.

docs/content/configuration/basics.md

@@ -90,18 +90,16 @@ the option will inherit from the default.
 
 Some options are available to customize how the `backup` command works.
 
-### Storage
+### Storage {#storage}
 
 #### Root directory
 
 The `storage_directory` parameter let you choose where to put the generated dumps.
 
-@@@ symfony
-Default value is `'%kernel.project_dir%/var/db_tools'`.
-@@@
-@@@ standalone docker
-Default value is `./var/db_tools'`.
-@@@
+Default value is
+<span db-tools-flavor="standalone">`./var/db_tools` (relative to the YAML config file)</span>
+<span db-tools-flavor="symfony">`%kernel.project_dir%/var/db_tools`</span>
+<span db-tools-flavor="docker">`/var/www/var/db_tools` (inside the docker container)</span>
 
 #### File and directory naming strategy
 
@@ -249,7 +247,7 @@ command using the `--exclude` option.
 
 See the [default binary options](#default-binary-options) section.
 
-### Backup expiration age
+### Backup expiration age {#backup-expiration-age}
 
 The `backup_expiration_age` parameter let you choose when a backup is considered
 as obsolete.

docs/content/getting-started/installation.md

@@ -1,8 +1,6 @@
 # Installation
 
-Installation method will depend on which flavor you want to use.
-
-Select below your target:
+Installation method will depend on which flavor you want to use:
 
 <FlavorSwitcher />
 
@@ -32,11 +30,9 @@ Currently supported database vendors:
 - MariaDB 10.11 and above
 - MySQL 5.7, 8.0 and above
 - SQLite 3.0 and above
-- SQL Server 2019 and above
-  <br><small>(previous versions from 2015 are untested but should work)</small>
 
 ::: info
-The bundle could also work with other database vendors.
+The library could also work with other database vendors.
 Check out the [supported database vendors](../getting-started/database-vendors) page.
 :::
 
@@ -91,17 +87,14 @@ cp vendor/makinacorpus/db-tools-bundle/config/packages/db_tools.yaml config/pack
 Feel free to read this configuration file, it will learn you basics about this bundle.
 @@@
 @@@ docker
-You can, for example, add the [*DbToolsBundle* image](https://hub.docker.com/r/makinacorpus/dbtoolsbundle) to your docker compose stack like this:
-
+You can add the [*DbToolsBundle* image](https://hub.docker.com/r/makinacorpus/dbtoolsbundle) to your docker compose stack like in this example:
 
 ```yaml
 version: '3.8'
 
 services:
   postgres:
-    container_name: postgres
     image: postgres:15
-    restart: always
     environment:
       POSTGRES_PASSWORD: password
       POSTGRES_DB: db
@@ -119,6 +112,7 @@ services:
       - site // [!code ++]
     volumes: // [!code ++]
       - ./db_tools.config.yaml:/var/www/db_tools.config.yaml // [!code ++]
+      - ./db_tools:/var/www/var/db_tools // [!code ++]
 
 networks:
   site:
@@ -135,15 +129,15 @@ cp vendor/makinacorpus/db-tools-bundle/config/db_tools.standalone.sample.yaml db
 ```
 
 Update this file to your needs. The only required parameter is `connections` in which you
-must provided a [URL connection string](../configuration/reference#connections).
+must provided a [connection string](../configuration/reference#connections).
 
 In our example, the connection string will be `pgsql://db:password@postgres:5432/db?version=15.0`.
 @@@
 
 **That's it, *DbToolsBundle* is now ready to be used.**
 
-But before starting to use it, check if it succeeds to find backup and
-restoration binaries for your Doctrine connection(s):
+But before starting to use it, check if it succeeds to find back up and
+restoration binaries for your database connection(s):
 
 @@@ standalone
 ```sh