Collective zc.buildout recipes

Add virtual mount point support for collective.recipe.filestorage

Reported by Jean Jordaan on 2009-08-05
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
collective.buildout
Undecided
Unassigned
Nominated for Trunk by Jean Jordaan

Bug Description

Zope allows mounting multiple storages into one ZODB.
Configuration of the mount point is done with the 'mount-point' directive in 'zope.conf'.
The full syntax of this directive is poorly documented. For the whole story, see Zope2/Startup/datatypes.py
I've added support for this syntax in the attached patch.
However, before getting all excited, have a look at https://bugs.launchpad.net/zope2/+bug/143144

Jean Jordaan (jean-jordaan) wrote :

Reworked patch, based on comments. Also fixes the signature of _subpart_option.

Michael Hierweck (hierweck) wrote :

collective.filestorage handles the defintion of filestorages more flexible than plone.recipe.zope2zeoserver/zope2instance do.

Can't we merge collective.filestorage into plone.recipe.zope2zeoserver/zope2instance so that is supports multiple filestorages out of the box?

Alternative: Can't we add an option (e.g. dont-gen-storage = true) to plone.recipe.zope2zeoserver/zope2instance so that is does not define any storages at all. All storages could be defined either using collective.filestorage or zope/zeo-conf-addtional then.

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

Other bug subscribers