collective.recipe.filestorage and base.cfg

Bug #513713 reported by Jean Jordaan on 2010-01-28
This bug affects 1 person
Affects Status Importance Assigned to Milestone
David Glick

Bug Description

I wanted to add collective.recipe.filestorage to the buildout created by 'zopeskel plone_hosting'.
I added a 'filestorage' part and '[filestorage]' stanza in 'buildout.cfg', which extends 'base.cfg'

This complained that the recipe needs at least one zope2instance part (in spite of this part being present in 'base.cfg').

I then moved the part name and the stanza to 'base.cfg', but this did nothing -- seems like the filestorage part doesn't get processed.

I finally moved them back to 'buildout.cfg', and moved the 'instance1' part and '[instance1]' stanza from 'base.cfg' to 'buildout.cfg', and now it works.

This feels like a lot of sacrificing of dead chickens.

Jean Jordaan (jean-jordaan) wrote :

I had to move the 'zeo' sections to 'buildout.cfg' as well -- so only the current file is scanned by the filestorage recipe, even though it extends another file.

Looks like the bug topic should really be: 'collective.recipe.filestorage' doesn't work with buildout's 'extends' functionality.

David Glick (davisagli) on 2010-02-04
Changed in collective.buildout:
assignee: nobody → David Glick (davisagli)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers