uli at gnufix.de
Wed Apr 15 04:49:19 EDT 2009
Hugo Lopes wrote:
> You don't need startup.py anymore. Now grok uses grokcore.startup and
> you don't need to worry about it.
> I'm not the better person to answer this question and I hope someone
> with more knowledge about it answer you.
> On Mon, Apr 13, 2009 at 1:57 PM, Tim Cook <timothywayne.cook at gmail.com> wrote:
> > Hi All,
> > I am quite confused over when and how startup.py is generated/created.
> > Especially so since Grok 1.0a3. I previously thought that grokproject
> > created it. Now I'm not so sure.
> > Since it contains hard coded links I need to know how this happens so
> > that I can correctly identify an install procedure for the users of my
> > grokproject based application.
Hugo is right, the whole stuff that was in former times generated in
local startup.py is now provided by the grokcore.startup package.
Instructions how to update old projects with a grokproject-generated
startup.py can be found here:
The WSGI application factory accepts a parameter ``zope_conf`` from
local conf, where you can specify the path to zope.conf. This variable
can for instance be set in your project's deploy.ini like this::
# set the name of the zope.conf file
zope_conf = %(here)s/zope.conf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://mail.zope.org/pipermail/grok-dev/attachments/20090415/14c787f4/attachment.bin
More information about the Grok-dev