Skip to content

Releases: jberends/duplicity_backup

v1.2.1

31 Jan 09:10
b0b9346
Compare
Choose a tag to compare

v1.2.1 (31JAN23)

  • 👍 Reinstating python 3.6 compatibility to ensure make it compatible with older installations that ship python 3.6.

v1.2.0

23 Jan 08:33
Compare
Choose a tag to compare

v1.2.0 (23JAN23)

This release is named "The Other S3 As Well"-Release. We now support other S3 storage providers, other than only the Amazon one. So now you can use digitalocean (tested) or even dropbox for that matter as a remote storage for your backups.

  • ⭐ Added the option extra_args in the configuration yaml. These extra_args may be provided as a list in the yaml and they are passed down to duplicity. See the duplicity documentation for the exact use of them. (#8)
  • ⭐ Added the option to provide the full remote uri in the yaml section remote > uri. This will circumvent the construction of the uri based on endpoint, bucket and path and ensures that when you know what you are doing a lot of different storage providers may be used. See the duplicity help documentation how to provide the remote uri correctly. (#8)
  • ⭐ Added GPG encryption possibilities. Thanks to @denismatveev. (#5)
  • ⭐ Added the ability to use custom S3 endpoints. Now it does not default to amazon S3 and you can use S3 compatible storage targets such as digitalocean (tested on Digital Ocean). Thanks to @denismatveev. (#5)
  • 👍 Improved init command to add a flag --quiet for less chatty way of initialisation of the config file. (#8)
  • 👍 Thorough spring cleanup. Dropped support for Python releases below 3.7. Black-ened, pyupgrade-ed, isort-ed the codebase. Fixed tests and added tests for newer python releases. Switched to dependabot for dependency management. (#8)

v1.1.0

08 Dec 21:26
Compare
Choose a tag to compare

v1.1.0 (8DEC20)

  • added restore command implementation.

v1.0.2

03 Apr 08:57
Compare
Choose a tag to compare

v1.0.2 (3APR20)

  • Added appdirs to the setup.py requirements.

v1.0.1 (UNLRELEASED)

Not released to the public.

v1.0.0 (16DEC19)

First production release.

  • implemented appdirs, such that the configuration file can be safely placed and located from a known configuration directory on disk.
  • added remove command to remove collections from the backup target after a specified time. Please consult the duplicity_backup_s3 remove --help documentation for guidance.
  • added init command to initialise the configuration in an interactive fashion for users.
  • various development improvements, eg Github actions for testing and publishing to PyPI; removed all flake8 warnings and pydocstyle errors. Added pre-commit hooks. Code is A++ grade now.

v1.0.0

17 Dec 10:55
Compare
Choose a tag to compare

v1.0.0 (16DEC19)

First production release

  • implemented appdirs, such that the configuration file can be safely placed and located from a known configuration directory on disk.
  • added remove command to remove collections from the backup target after a specified time. Please consult the duplicity_backup_s3 remove --help documentation for guidance.
  • added init command to initialise the configuration in an interactive fashion for users.
  • various development improvements, eg Github actions for testing and publishing to PyPI; removed all flake8 warnings and pydocstyle errors. Added pre-commit hooks. Code is A++ grade now.

v0.5.0

04 Jun 20:10
Compare
Choose a tag to compare

v0.5.0 (5JUN19)

First initial public release

  • commands incr, list, status, verify, cleanup implemented.
  • added yaml schema check for the configuration file.

Features

This is a duplicity command line backup wrapper that will backup to S3 that is using a validated yaml configuration file using modern and awesome CLI patterns. The commands incremental, list files, status, verify, cleanup, and remove are implemented.

The primary use case to build this (yet another one) CLI wrapper for duplicity to be able to deploy the command in production and inject it into a cron.daily and having a hands-off automated backup of production servers. We use it a KE-works to automate our production server backups.