[Zope-dev] who wants to maintain Zope 3?
Roger Ineichen
dev at projekt01.ch
Tue Apr 14 12:12:48 EDT 2009
Hi Martijn
> -----Ursprüngliche Nachricht-----
> Von: zope-dev-bounces at zope.org
> [mailto:zope-dev-bounces at zope.org] Im Auftrag von Martijn Faassen
> Gesendet: Dienstag, 14. April 2009 17:54
> An: zope-dev at zope.org
> Betreff: Re: [Zope-dev] who wants to maintain Zope 3?
>
> Hey,
>
> Baiju M wrote:
> [snip]
> > Does Zope Tookit support building a web application out of the box
> > without relying on Grok, Zope 2 or any other framework ?
> > (I am Ok to use a Buildout for building application from
> Zope Toolkit
> > packages)
>
> This is a very good question. My answer is "no, it doesn't".
> It might support tools to help construct such "out of the
> box" experiences, but it won't be something you can install
> and just get started with unless you really want to roll your
> own framework.
>
> > If the answer to this question is "No", then I am interested to
> > maintain the packages necessary to create a simple
> application out of the box.
> > This is just an academic interest :)
>
> Great!
>
> We should definitely have Zope 2 and Plone and Grok and Zope
> 3 work together and share experience. I have the feeling each
> project is working isolated from each other now, and with
> Grok we're moving to paste and I just have the feeling we're
> inventing some of our own wheels that could be shared, or
> alternatively that we shouldn't be doing that way. Currently
> for instance we generate "debug.ini" and such and put them in
> "parts" as they have hardcoded path names. That can't be right...
Take a look at the z3c.recipe.paster:serve recipe
You can define your WSGI app in a buildout.cfg file like:
[app]
recipe = z3c.recipe.paster:serve
eggs = MYPYPI
ini =
[filter-app:main]
use = egg:Paste#translogger
next = zope
[app:zope]
use = egg:MYPYPI
fsStorage = ${buildout:directory}/parts/fsstorage
tmpStorage = ${buildout:directory}/parts/tmpstorage
[server:main]
use = egg:Paste#http
host = localhost
port = 8080
zope.conf =
${var:zconfig}
devmode on
<eventlog>
<logfile>
formatter zope.exceptions.log.Formatter
path ${buildout:directory}/parts/logs/error.log
</logfile>
<logfile>
formatter zope.exceptions.log.Formatter
path STDOUT
</logfile>
</eventlog>
site.zcml =
<configure
xmlns="http://namespaces.zope.org/zope"
xmlns:meta="http://namespaces.zope.org/meta">
<meta:provides feature="devmode" />
<include package="mypypi" file="app.zcml" />
</configure>
after run buildout you can call
bin/app
Regards
Roger Ineichen
_____________________________
END OF MESSAGE
> Regards,
>
> Martijn
>
>
> _______________________________________________
> Zope-Dev maillist - Zope-Dev at zope.org
> http://mail.zope.org/mailman/listinfo/zope-dev
> ** No cross posts or HTML encoding! ** (Related lists -
> http://mail.zope.org/mailman/listinfo/zope-announce
> http://mail.zope.org/mailman/listinfo/zope )
>
More information about the Zope-Dev
mailing list