Any content mounted to /var/backups/in
will be included into the backup:
docker run --rm -i \
-v path/to/backup:/var/backups/in:ro \
-v target:/var/backups/out \
jnbt/tartarus
You can perform incremental backups using app:start -i
but you should mount
a persistend volume to /var/backups/timestamps
otherwise Tartarus cannot
determine the updated files:
docker run --rm -i \
-v path/to/backup:/var/backups/in:ro \
-v target:/var/backups/out \
-v timestamps:/var/backups/timestamps \
jnbt/tartarus \
app:start -i
You can use the full power of Tartarus by providing
an own set of backup configurations. The container will automatically run any *.conf
-configuration
provided at /var/backups/conf
:
docker run --rm -i \
-v conf:/var/backups/conf:ro \
-v path/to/backup:/var/backups/in:ro \
-v timestamps:/var/backups/timestamps \
...
jnbt/tartarus
Tartarus is assuming the encription passphrase in a file. You may either mount
the passphrase-file into the container or provide a ENCRYPT_PASSPHRASE
environment variable which will be stored at /var/backups/passphrase
.
Makefile
: BumpVERSION
Dockerfile
: BumpTARTARUS_VERSION
andRELEASE_DATE
README.md
: Bump versions inSoftware
section- Run
make release