Grok without ZODB, WSGI based
When Google released its appengine SDK this Monday i started to explore a potential integration with Grok immediately. There are several problems that need to be solved, but i'm confident that the zope3 libs will be used with appengine apps in the future.
When tinkering with Grok/appengine i wanted at one point to rip off the ZODB dependency. That was suprisingly easy to achieve - it took an afternoon to get it running - and i must say that using Grok as a WSGI app was the part that made it possible at all.
I just posted d2m.wsgiapp to PyPI - this is a package that lets you run Grok without a ZODB as a WSGI application. It uses a custom root object and a custom publication. A demo application is also included for testing.
I'd really appreciate your feedback on the package.
Moreover - parts of Grok already integrate with the appengine framework. I now have a grok app running with the Google appengine.datastore as DB backend.
Next stop is - amazingly - re-adding the ZODB as a pluggable datastorage. You are welcome to join the project.
Comment
So in short, Grok does not run with appengine, but i'm sure the attempt to integrate it will create new possibilities for Grok.
Comment
Comment
as for appengine, there are several issues with running zope on appengine, the c modules prevent basic things like zope.component from working.. and thats just one of several. assuming pure python implmentations are used, just as serious is the 1000 file limit imposed by app engine which requires reworking template/zcml to run from zip safe eggs.
Comment
Things are a bit different with Grok and it took me some time to get the paster configuration setup and the appsetup right to integrate with the Grok infrastructure. I also wanted to promote the idea of a ZODB-less Grok just before the Grokkerdam sprint happening. Hope sprinters there will get to it and take it even further.
Comment