plone.recipe.zope2zeoserver ?generates? zeoctl and runzeo with incorrect PYTHONPATH and ZODB3_HOME

[ken manheimer]

i'm actually very unclear about where the responsibility lies for the failure of proper PYTHONPATH and ZODB3_HOME settings in the generated bin/runzeo and bin/zeoctl scripts. i am trying to use plone.recipe.zope2zeoserver in combination with andi zeidler's adaptation to use a blob-aware-ZODB version of Zope with plone, and unable to get it to make the right settings. plone.recipe.zope2instance does the right thing for the client's bin/runzope and bin/zopectl, however.

see http://myriadicity.net/Sundry/PloneBlobs for details.

[LeoRochael (leorochael)]

ZODB3_HOME is a rather useless variable that goes back to the monolithic days of full Zope installations. It's a single path that is supposed to be added to PYTHONPATH and contain a ZODB distribution and all its dependencies, like ZConfig and zdaemon.

On my branch at:
https://svn.plone.org/svn/collective/buildout/plone.recipe.zope2zeoserver/branches/rochael-blobsupport

I'm extending the zope2zeoinstance strategy of patching the script files and setting more appropriate values.

[LeoRochael (leorochael)]

Code commited, Please test.

[ken manheimer (ken-manheimer)]

i can confirm that your version of plone.recipe.zope2zeoserver resolves the problems i was seeing! the server's zeo.conf has the correct blobstorage storage declaration, and the server's bin/runzeo and bin/zeoctl scripts have the right ZODB_HOME and PYTHONPATH settings. thanks!

[Hanno Schlichting (hannosch)]

The branch is merged to trunk, new release follows shortly after I get a comment on 'blob-cache-writable' mentioned in https://bugs.launchpad.net/collective.buildout/+bug/179115.

[Hanno Schlichting (hannosch)]

0.9 releease is out.