Collective zc.buildout recipes

Please add read-only database option to plone.recipe.zope2instance

Reported by Alex Clark on 2011-02-03
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
collective.buildout
Wishlist
Unassigned

Bug Description

Based on the suggestion to implement a read-only database in http://plone.org/products/plone/security/advisories/cve-2011-0720, and since there is currently no support for this in plone.recipe.zope2instance, I am opening this bug to suggest it be added.

See: http://plone.293351.n2.nabble.com/Putting-databases-in-read-only-mode-td5984209.html for more information.

Thanks to Alex.

http://plone.org/documentation/faq/plone-read-only-mode now includes a link to this suggestion.

Hanno Schlichting (hannosch) wrote :

I don't think adding the read-only option is a good approach here. The recipe should rather support a custom-database option to provide the entire database snippet. With file storage, ZEO, RelStorage and various blobwrappers or storages for these, there's too many options that influence those.

It's actually much more explicit and clearer to write the entire storage snippets inside the buildout.cfg (with variable replacement for the directory base parts). Replicating the nested storage config in a set of flat buildout options is just confusing for any non-trivial case.

Alex Clark (aclark) wrote :

OK So that's a +1 from Elro (+1. It shouldn't be difficult to add, though it will adding in several places, once for each storage type. The recipe shows clear signs of organic growth over the years... ) and a -1 from Hanno :-)

Personally, I don't care whether I have to enter a "snippet" or whether I enter "read-only = true". The latter would be easier but if the former makes the most sense that's fine with me.

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

Other bug subscribers