[Grok-dev] Re: the checking-your-project-back-out story

Martijn Faassen faassen at startifact.com
Mon Apr 28 09:32:02 EDT 2008

Wichert Akkerman wrote:
> Previously Brandon Craig Rhodes wrote:
>> Another option is possible beyond the ones I listed, by the way: we
>> could give the "grokproject" command the ability to operate upon an
>> existing Grok project, instead of only being able to create new ones.
>> That way they could:
>>   $ svn co .../myproject
>>   $ grokproject myproject
>>   Rebuild/repair existing Grok project 'myproject'? [yn] y
>>   $ cd myproject
>>   $ bin/zopectl fg
>> and be up and running.  This way we would not have to include the
>> extra clutter of a "bootstrap.py" file whose purpose beginning users
>> might be confused about.  We could also hide from them the fact that
>> two buildout-like steps (bootstrap then buildout) are involved.

I think that's a good approach.

> paste can already do that. I think grokproject should be rewritten to be
> just a paste template, similar to, for example, the plone hosting
> template.

Hm, grokproject has always been using paste. What specific modification 
to grokproject are you suggesting?



More information about the Grok-dev mailing list