Collective zc.buildout recipes

collective.recipe.backup additional and filestorage

Reported by Jean Jordaan on 2010-04-30
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
collective.buildout
Undecided
Unassigned

Bug Description

In my [filestorage] buildout part, I have:

location = var/filestorage/%(fs_part_name)s/%(fs_part_name)s_Data.fs

The collective.recipe.backup recipe seems to assume that all filestorages will be siblings.
I think it will work if I jam the directory into the additional_filestorages configuration:

additional_filestorages =
    catalog/catalog_Data
    another/another_Data

but I think this is unintentional.

Ideally, the [backup] part should be able to let additional_filestorages default to the storages configured by the collective.recipe.filestorage configuration.

Would this be possible?

Reinout van Rees (reinout) wrote :

Well, the backup recipe is intended to allow easy backups: "drop in these two lines and your backup script is ready".

So if you can make it work with auto-detecting collective.recipe.filestorage part(s): fine with me. I can't see right away how easy that would be: the part(s) can be named anything, so you'd have to detect the used recipe somehow.

If it would make the recipe's code 2 times as big, a small shell script to replace bin/backup would be better :-)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers