Collective-recipe-backup

Latest version: v4.0

Safety actively analyzes 715081 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 6 of 9

2.1

================

- Raise an error when the four backup location options
(blobbackuplocation, blobsnapshotlocation, location and
snapshotlocation) are not four distinct locations (or empty
strings).
[maurits]

- Fixed possible TypeError: 'Option values must be strings'.
Found by Alex Clark, thanks.
[maurits]

2.0

================

- Backup and restore blobs, using rsync.
[maurits]

- Ask if the user is sure before doing a restore.
[maurits]

1.7

================

- Fix generated repozo commands to work also
when recipe is configured to have a non **Data.fs**
main db plus additional filestorages.
e.g.:
datafs= var/filestorage/main.fs
additional = catalog
[hplocher]

1.6

================

- Added the option enable_snapshotrestore so that the creation of the
script can be removed. Backwards compatible, if you don't specify it
the script will still be created. Rationale: you may not want this
script in a production buildout where mistakenly using
snapshotrestore instead of snapshotbackup could hurt.
[fredvd]

1.5

================

- Fix: when running buildout with a config in a separate directory
(like ``bin/buildout -c conf/prod.cfg``) the default backup
directories are no longer created inside that separate directory.
If you previously manually specified one of the location,
snapshotlocation, or datafs parameters to work around this, you can
probably remove those lines. So: slightly saner defaults.
[maurits]

1.4

================

- Added documentation about how to get the required bin/repozo script
in your buildout if for some reason you do not have it yet (like on
Plone 4 when you do not have a zeo setup).
Thanks to Vincent Fretin for the extra buildout lines.
[maurits]

Page 6 of 9

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.