Don't generate a starting script in plone.recipe.zope2instance

Bug #710535 reported by Sylvain Viollon on 2011-01-31
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Hanno Schlichting

Bug Description


   I use plone.recipe.zope2instance to create a Zope 2 instance that I serve using WSGI, with other middlewares. The recipe is still very usefull to me to create the instance skeleton with the configuration file and all the ZCML plugs, however I dont' use anymore the generated instance script.

   My issue is that my customers used to start Zope with that script, and of course, since nobody reads documentation, they don't know they have to start it with paster now or some other WSGI server now, and miss some middlewares at runtime.

   So I would like to have the possibility not to generate a starting script, if possible, like a option no-script = true would be great.

  Thank you very much for your hard work !

Hanno Schlichting (hannosch) wrote :

The zope2instance recipe isn't really useful for WSGI deployments. It does so much stuff that's not useful in this environment, that I'd rather not support it.

We should make a new much more minimal recipe for running zope2 wsgi instances. This new recipe can skip the whole zope.conf generation part and just do something like collective.recipe.template. The amount of things you'll need in a zope.conf are quite minimal now.

Changed in collective.buildout:
assignee: nobody → Hanno Schlichting (hannosch)
status: New → Won't Fix
Sylvain Viollon (thefunny) wrote :

Yes, well I am not against that, but there is still quite lot of things to support in the zope.conf: all the database configuration / ZEO / Relstorage support / Blob, the ZCML inclusions, all non-server related options (there are quite lot of them), all the directories to create.

I was thinking at first to have a collective.recipe.template that is able to create a template out of an archive (folder skeleon), and use the files as a template, however I didn't want to duplicate the effort done on having an up to date and working template for the zope.conf configuration file. But I guess I will still work on something like that.

Hanno Schlichting (hannosch) wrote :

I started experimenting with a Zope2 WSGI setup myself. The zope.conf file isn't really all that long, I came up with for Plone - a lot of things you can throw out for the general Zope case.

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

Other bug subscribers