|
| 1 | +db_tools: |
| 2 | + # Where to put generated backups. |
| 3 | + # Root directory of the backup storage manager. Default filename |
| 4 | + # strategy will always use this folder as root path. |
| 5 | + #storage_directory: '%kernel.project_dir%/var/db_tools' |
| 6 | + |
| 7 | + # Filename strategies. You may specify one strategy for each doctrine |
| 8 | + # connection. Keys are doctrine connection names. Values are strategy |
| 9 | + # names, "default" (or null) or omitting the connection will use the |
| 10 | + # default implementation. |
| 11 | + # If you created and registered a custom one into the container as a |
| 12 | + # service, you may simply set the service identifier. If no service |
| 13 | + # exists, and your implementation does not require parameters, simply |
| 14 | + # set the class name. |
| 15 | + # Allowed values are: |
| 16 | + # - "default": alias of "datetime". |
| 17 | + # - "datetime": implementation is "%db_tools.storage_directory%/YYYY/MM/<connection-name>-<datestamp>.<ext>". |
| 18 | + # - CLASS_NAME: a class name to use that implements a strategy. |
| 19 | + # - SERVICE_ID: A service identifier registered in container that |
| 20 | + # implements a strategy. |
| 21 | + #storage_filename_strategy: default |
| 22 | + |
| 23 | + # When old backups are considered obsolete. |
| 24 | + # (Use relative date/time formats : https://www.php.net/manual/en/datetime.formats.relative.php) |
| 25 | + #backup_expiration_age: '6 months ago' # default '3 months ago' |
| 26 | + |
| 27 | + # Default timeout for backup process. |
| 28 | + #backup_timeout: 1200 # default 600 |
| 29 | + |
| 30 | + # Default timeout for restore process. |
| 31 | + #restore_timeout: 2400 # default 1800 |
| 32 | + |
| 33 | + # List here tables you don't want in your backups. |
| 34 | + # If you have more than one connection, it is strongly advised to configure |
| 35 | + # this for each connection instead. |
| 36 | + #backup_excluded_tables: ['table1', 'table2'] |
| 37 | + |
| 38 | + # Specify here paths to backup and restoration binaries and command line |
| 39 | + # options. |
| 40 | + # Warning: this will apply to all connections disregarding their database |
| 41 | + # vendor. If you have more than one connection and if they use different |
| 42 | + # database vendors or versions, please configure those for each connection |
| 43 | + # instead. |
| 44 | + # Default values depends upon vendor and are documented at |
| 45 | + # https://dbtoolsbundle.readthedocs.io/en/stable/configuration.html |
| 46 | + #backup_binary: '/usr/bin/pg_dump' |
| 47 | + #backup_options: '-Z 5 --lock-wait-timeout=120' |
| 48 | + #restore_binary: '/usr/bin/pg_restore' |
| 49 | + #restore_options: '-j 2 --clean --if-exists --disable-triggers' |
| 50 | + |
| 51 | + # For advanced usage, you may also override any parameter for each connection. |
| 52 | + # Each key is a connection name, all parameters above are allowed for each |
| 53 | + # unique connection. |
| 54 | + # Keys are doctrine connection names. |
| 55 | + #connections: |
| 56 | + # connection_one: |
| 57 | + # # Complete list of accepted parameters follows. |
| 58 | + # url: "pgsql://username:password@hostname:port?version=16.0&other_option=..." |
| 59 | + # backup_binary: /usr/local/bin/vendor-one-dump |
| 60 | + # backup_excluded_tables: ['table_one', 'table_two'] |
| 61 | + # backup_expiration_age: '1 month ago' |
| 62 | + # backup_options: --no-table-lock |
| 63 | + # backup_timeout: 2000 |
| 64 | + # restore_binary: /usr/local/bin/vendor-one-restore |
| 65 | + # restore_options: --disable-triggers --other-option |
| 66 | + # restore_timeout: 5000 |
| 67 | + # storage_directory: /path/to/storage |
| 68 | + # storage_filename_strategy: datetime |
| 69 | + # connection_two: |
| 70 | + # # ... |
| 71 | + |
| 72 | + # Update this configuration if you want to look for anonymizers in a custom |
| 73 | + # folder. |
| 74 | + # Be aware that DbToolsBundle will always take a look at the default folder |
| 75 | + # dedicated to your custom anonymizers: %kernel.project_dir%/src/Anonymizer, |
| 76 | + # so you don't have to repeat it. |
| 77 | + #anonymizer_paths: |
| 78 | + # - '%kernel.project_dir%/src/Database/Anonymizer' |
| 79 | + |
| 80 | + # For simple needs, you may simply write the anonymization configuration |
| 81 | + # here. Keys are connection names, values are structures which are identical |
| 82 | + # to what you may find in the "anonymizations.sample.yaml" example. |
| 83 | + #anonymization: |
| 84 | + # connection_one: |
| 85 | + # table1: |
| 86 | + # column1: |
| 87 | + # anonymizer: anonymizer_name |
| 88 | + # # ... anonymizer specific options... |
| 89 | + # column2: |
| 90 | + # # ... |
| 91 | + # table2: |
| 92 | + # # ... |
| 93 | + # connection_two: |
| 94 | + # # ... |
| 95 | + |
| 96 | + # You can for organisation purpose delegate anonymization config into extra |
| 97 | + # YAML configuration files, and simply reference them here. |
| 98 | + # Paths can be either relative or absolute. Relative paths are relative to |
| 99 | + # the workdir option if specified, or from this configuration file directory |
| 100 | + # otherwise. |
| 101 | + # See the "anonymizations.sample.yaml" in this folder for an example. |
| 102 | + #anonymization_files: |
| 103 | + # connection_one: '%kernel.project_dir%/config/anonymization/connection_one.yaml' |
| 104 | + # connection_two: '%kernel.project_dir%/config/anonymization/connection_two.yaml' |
| 105 | + |
| 106 | + # If you have only one connection, you can adopt the following syntax. |
| 107 | + anonymization_files: '%kernel.project_dir%/config/anonymizations.yaml' |
0 commit comments