Tres has managed to merge his WSGI branch into trunk and Hanno tells me the unofficial plan is to include this in a release for Zope 2.13, in time for Plone 4.1. This is not decided upon yet though.
I was planning on implementing WSGI for Zope2 during the Penn State Symposium Sprints, and I did a few things to help out; however, Tres Seaver did most of the work on his own before and during part of the Sprint :) The rest of the time I spent just testing it out and helping with the Theme Editor sprint.
Now, it's really quite trivial to get it working now and makes all of the repoze.zope2 nonsense unneeded now. This article is just here for a reference if anyone else is interested in getting it going on their setup.
This guide assumes you have an existing Plone 4 installation to work from. I don't provide any buildouts here--just modifying an existing buildout to make it work with a branch of Zope2 and creating an ini that Paste can consume to serve WSGI.
Supplying the WSGI'd Zope2
First off, go to the src directory of the installation. If you've installed using the unified installer, that will bin in instance-home/zinstance/src or if you just used straight buildout, it'll be in instance/src. Then checkout the Zope2 branch:
svn co http://svn.zope.org/repos/main/Zope/branches/tseaver-fix_wsgi/ Zope2
Stringing up buildout
Next thing you'll need to do is modify your buildout.cfg file to add the checked out Zope 2 to the develop section:
Still modifying your buildout.cfg, add Paste, PasteScript, repoze.tm2 and repoze.retry to your eggs section:
Again, editing your buildout.cfg, add a paster part for the paster script:
Then, you'll need to add the updated Zope2 versions for the WSGI branch. To do this, basically, just add the versions.cfg file provided in the branch after every other version file listed in the extends directive. It'll look like this:
Then run your buildout like normal:
Creating a WSGI Configuration File
You'll now need to create a WSGI configuration file. Right now, we'll just server it using the Paste server and wsgi ini configuration way. You can also do this to string up Apache's WSGI implementation but that is beyond the scope of this article.
Create a file in the instance directory called, zope2.ini with the contents of:
[app:zope] use = egg:Zope2#main zope_conf = %(here)s/parts/instance/etc/zope.conf [pipeline:main] pipeline = egg:paste#evalerror egg:repoze.retry#retry egg:repoze.tm2#tm zope [server:main] use = egg:paste#http host = localhost port = 8080
The zope_conf value in the app:zope section can be the path to any zope.conf file. I'm just exampling the standard location of it and not going through the configuration of that file itself.
Fire it up!
If all went well, you should now be able to start up your Plone 4 instance on WSGI like this:
./bin/paster serve zope2.ini
Your server should now be able to visit your site on http://localhost:8080
I did run into a snag with the Mac OS X unified installer and the version of python it has configured. Basically, it wouldn't compile the Zope2 dependencies so I had to use my own version of python that I had compiled with the python buildout found in the plone collective svn. The bug is sort of referenced in the zope bug tracker.
I'm hoping to maybe get a release with this branch implementation out--maybe as an alpha or beta release since I don't think they are planning on merging this to core any time soon; although, I really have no understanding of what that whole process is.
I'd like to see the Zope2 package implement mkzope2instance and other convenience methods so it'd be possible to install Plone 4/Zope2 without buildout at all maybe using pip. I'm looking into how this might be able to happen with a pip versions file and other things. Maybe more on this later.
Post any comments if you run into any issues.