offen/docker-volume-backup
1
1
Fork 0
mirror of https://github.com/offen/docker-volume-backup.git synced 2025-09-06 14:37:44 +08:00
Code Issues Projects Releases Packages Wiki Activity

Documentation should not mention deprecated version declaration

Browse source
This commit is contained in:
Frederik Ring 2025-06-07 16:01:50 +02:00
parent 06bb25c980
commit 47a9c13b54
10 changed files with 0 additions and 56 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
docs/how-tos/automatically-prune-old-backups.md
View file

@ -14,8 +14,6 @@ Be aware that this mechanism looks at __all files in the target bucket or archiv
In case you need to use a target that cannot be used exclusively for your backups, you can configure `BACKUP_PRUNING_PREFIX` to limit which files are considered eligible for deletion:
```yml
version: '3'
services:
# ... define other services using the `data` volume here
backup:

2
docs/how-tos/handle-file-uploads-using-third-party-tools.md
View file

@ -20,8 +20,6 @@ RUN apk add rsync
Using this image, you can now omit configuring any of the supported storage backends, and instead define your own mechanism in a `docker-volume-backup.copy-post` label:
```yml
version: '3'
services:
backup:
image: your-custom-image

2
docs/how-tos/replace-deprecated-backup-from-snapshot.md
View file

@ -11,8 +11,6 @@ Starting with version 2.15.0, the `BACKUP_FROM_SNAPSHOT` feature has been deprec
If you need to prepare your sources before the backup is taken, use `archive-pre`, `archive-post` and an intermediate volume:
```yml
version: '3'
services:
my_app:
build: .

6
docs/how-tos/run-custom-commands.md
View file

@ -28,8 +28,6 @@ the `docker-volume-backup` container as shown in the Quickstart example.
Taking a database dump using `mysqldump` would look like this:
```yml
version: '3'
services:
# ... define other services using the `data` volume here
database:
@ -56,8 +54,6 @@ In case you use `EXEC_LABEL` together with configuration mounted from `conf.d` i
Else, schedules that do not specify an `EXEC_LABEL` will still trigger commands on all containers with such labels, no matter whether they specify `docker-volume-backup.exec-label` or not.
```yml
version: '3'
services:
database:
image: mariadb
@ -87,8 +83,6 @@ By default the backup command is executed by the user provided by the container'
It is possible to specify a custom user that is used to run commands in dedicated labels with the format `docker-volume-backup.[step]-[pre|post].user`:
```yml
version: '3'
services:
gitea:
image: gitea/gitea

2
docs/how-tos/run-multiple-schedules.md
View file

@ -10,8 +10,6 @@ nav_order: 11
Multiple backup schedules with different configuration can be configured by mounting an arbitrary number of configuration files (using the `.env` format) into `/etc/dockervolumebackup/conf.d`:
```yml
version: '3'
services:
# ... define other services using the `data` volume here
backup:

2
docs/how-tos/set-container-timezone.md
View file

@ -12,8 +12,6 @@ As the image is designed to be as small as possible, additional timezone data is
In case you want to run your cron rules in your local timezone (respecting DST and similar), you can mount your Docker host's `/etc/timezone` and `/etc/localtime` in read-only mode:
```yml
version: '3'
services:
backup:
image: offen/docker-volume-backup:v2

2
docs/how-tos/set-up-notifications.md
View file

@ -12,8 +12,6 @@ parent: How Tos
To send out email notifications on failed backup runs, provide SMTP credentials, a sender and a recipient:
```yml
version: '3'
services:
backup:
image: offen/docker-volume-backup:v2

2
docs/how-tos/stop-containers-during-backup.md
View file

@ -17,8 +17,6 @@ By default, any container that is labeled `docker-volume-backup.stop-during-back
In case you need more fine grained control about which containers should be stopped (e.g. when backing up multiple volumes on different schedules), you can set the `BACKUP_STOP_DURING_BACKUP_LABEL` environment variable and then use the same value for labeling:
```yml
version: '3'
services:
app:
# definition for app ...

2
docs/index.md
View file

@ -32,8 +32,6 @@ Code and documentation for `v1` versions are found on [this branch][v1-branch].
Add a `backup` service to your compose setup and mount the volumes you would like to see backed up:
```yml
version: '3'
services:
volume-consumer:
build:

34
docs/recipes/index.md
View file

@ -15,8 +15,6 @@ This doc lists configuration for some real-world use cases that you can copy and
## Backing up to AWS S3
```yml
version: '3'
services:
# ... define other services using the `data` volume here
backup:
@ -36,8 +34,6 @@ volumes:
## Backing up to Filebase
```yml
version: '3'
services:
# ... define other services using the `data` volume here
backup:
@ -58,8 +54,6 @@ volumes:
## Backing up to MinIO
```yml
version: '3'
services:
# ... define other services using the `data` volume here
backup:
@ -81,8 +75,6 @@ volumes:
## Backing up to MinIO (using Docker secrets)
```yml
version: '3'
services:
# ... define other services using the `data` volume here
backup:
@ -112,8 +104,6 @@ secrets:
## Backing up to WebDAV
```yml
version: '3'
services:
# ... define other services using the `data` volume here
backup:
@ -134,8 +124,6 @@ volumes:
## Backing up to SSH
```yml
version: '3'
services:
# ... define other services using the `data` volume here
backup:
@ -157,8 +145,6 @@ volumes:
## Backing up to Azure Blob Storage
```yml
version: '3'
services:
# ... define other services using the `data` volume here
backup:
@ -180,8 +166,6 @@ volumes:
See [Dropbox Setup](../how-tos/set-up-dropbox.md) on how to get the appropriate environment values.
```yml
version: '3'
services:
# ... define other services using the `data` volume here
backup:
@ -202,8 +186,6 @@ volumes:
## Backing up locally
```yml
version: '3'
services:
# ... define other services using the `data` volume here
backup:
@ -223,8 +205,6 @@ volumes:
## Backing up to AWS S3 as well as locally
```yml
version: '3'
services:
# ... define other services using the `data` volume here
backup:
@ -245,8 +225,6 @@ volumes:
## Running on a custom cron schedule
```yml
version: '3'
services:
# ... define other services using the `data` volume here
backup:
@ -268,8 +246,6 @@ volumes:
## Rotating away backups that are older than 7 days
```yml
version: '3'
services:
# ... define other services using the `data` volume here
backup:
@ -292,8 +268,6 @@ volumes:
## Encrypting your backups symmetrically using GPG
```yml
version: '3'
services:
# ... define other services using the `data` volume here
backup:
@ -314,8 +288,6 @@ volumes:
## Encrypting your backups asymmetrically using GPG
```yml
version: '3'
services:
# ... define other services using the `data` volume here
backup:
@ -341,8 +313,6 @@ volumes:
## Using mariadb-dump/mysqldump to prepare the backup
```yml
version: '3'
services:
database:
image: mariadb:latest
@ -367,8 +337,6 @@ volumes:
## Running multiple instances in the same setup
```yml
version: '3'
services:
# ... define other services using the `data_1` and `data_2` volumes here
backup_1: &backup_service
@ -402,8 +370,6 @@ volumes:
## Running as a non-root user
```yml
version: '3'
services:
# ... define other services using the `data` volume here
backup: