Comment 3 for bug 407458

Thanks Steve and Reinout for bringing this up!

Honestly, I am not sure, what the best way is.

The main problem is, that with the switch to paster, we need the (generated) zope.conf in a different location (same as deploy.ini) and we cannot use zc.recipe.zope3recipe anymore (please correct me if I'm wrong!).

Then, we left the [data] and [log] section in buildout.cfg, merely to create the directories parts/data/ and parts/log when buildout runs. This is hardly proper use of zc.recipe.filestorage but, well, okay. Maybe we can live with it.

I see the following options:

1) In zope.conf.in we replace the upper part (before <eventlog>) with something like:

     ${data:zconfig}

That would mean, that setting "blob-dir" in buildout.cfg and rerunning buildout would work again. For several reasons we could not easily drop the zope.conf.in template completely. We would also lose the ZEO config example which currently is part of zope.conf.in.

2) In zope.conf.in we could add a (commented) blob-storage definition as proposed by Steve. In buildout.cfg we could at the same time leave a comment where the blob-storage can be enabled (in zope.conf.in).

As you both are apparently the guys with a need for the blob-dir-option (or some replacement), you have to decide what way would suit your needs best. Maybe you also have an example configuration you would like to see in standard grokprojects? Otherwise I'd put something in like you, Steve, proposed on grok-dev.

Please note, that I hadn't heard of that option before your posts and therefore didn't mind when the whole configuration of grokproject changed (thanks for the hint!).

What do you think?