New über-buildout with Repoze and Deliverance

It appears also to be based on the good-py I created, though I wonder why you are not extending it directly:
http://good-py.appspot.com/release/repoze.zope2/1.0.

I wonder what you think of making plone.recipe.zope2instance and plone.recipe.zope2zeoserver support repoze? I fiddled with this here: http://svn.plone.org/[…]/ and here: http://svn.plone.org/[…]/
and plan to keep working on it.

The idea would be that we try make it easier for people to just "swap out" Zope2 w/Repoze.

Heh, sorry :)

I don't extend any remote services in the uber-buildouts, because I don't want to be dependent on a live internet connection for production deployment (this presumes you have a warm egg cache, of course).

plone.recipe.zope2zeoserver and plone.recipe.zope2instance do support repoze, in a sense. They're used in this setup. There's no magic repoze script or command runner in the build.

There's also a plone.recipe.repoze2instance, I think, that Hanno made.

The ZEO server side is identical anyway. The client side just needs a valid zope.conf, so really we could just generate that with collective.recipe.template.

Martin

Very useful piece of code. Thanks!
I'm glad that my work was also helpful :)

But zope on wsgi still have some problems. One of it you found some time ago: http://thread.gmane.org/[…]/focus=714

Is it fixed now? Or you just work without this functionality?

cool stuff, martin!

would you care to add munin to the mix? i could send you recipes to set it up, add zope-specific plugins and lighttpd to serve the graphs...

Nice Buildout : ) I already use(d) HAProxy / Varnish its nice to have a comprehensive buildout to play with.
On a side note it may be an idea to put in lxml deps (python-libxml2 / libxslt-dev ) which it cant be built without which caught me out for a few mins..

Looking forward to Uber Plone 4 Buildout.. : )