[Grok-dev] Re: an application installation script?

Jim Washington jwashin at vt.edu
Fri Oct 5 08:03:02 EDT 2007

Martijn Faassen wrote:
> Philipp von Weitershausen wrote:
>> Martijn Faassen wrote:
> [snip]
>>> It should be done somewhere between the end of the buildout and the
>>> first application startup to make this work.
>> I'm not sure what buildout has to do with it. Of course it happens
>> during the first application startup. That's why I think it should be
>> a setting in the app startup code/configuration. Which is the
>> Pastedeploy configuration file (called deploy.ini in zopeproject).
> It depends on ones installation philosophy. If we assume the
> information is in the ZODB the end of the buildout process could get
> up the ZODB in the right way. If you assume we use with Paste, it's on
> the filesystem and you'd use that explicitly.
> I don't have an immediate preference for either. The benefit of
> storing this configuration in the ZODB is that you could make a UI for
> it much more easily. This make sense for "beginner deployment"
> scenarios. We could probably also tackle this with a separate server
> startup script (or option) that always deploys the application you
> created with grokproject to "localhost:8080". This could then also do
> the right daemonizing and so on.
> For advanced deployment scenarios it becomes important to store this
> information in the filesystem and to be able to lock down things.
FWIW, I would also like for grok to have a place where the root object,
whatever it might be, to look for things that need to be in /.  I'm
thinking, in particular, robots.txt and favicon.ico.

-Jim Washington

More information about the Grok-dev mailing list