[Grok-dev] Grokproject - Best Practices??

[Leonardo Rochael Almeida]

Hi Tim,

Your second approach makes more sense. And BTW, you don't need to tell
your users to install zc.buildout either. "bootstrap.py" takes care of
that for you, using zc.buildout as an egg.

Cheers,
Leo

PS: looking forward to meeting you on FISL 10 :-)

On Thu, Apr 16, 2009 at 07:01, Tim Cook <timothywayne.cook at gmail.com> wrote:
>
> Before I spend a lot of time experimenting with options I would like to
> get some feedback from the experts here.
>
> My project was originally based on grokproject 0.14  now upgraded to
> 1.0a3.
>
> My current installation instructions include the user to install
> grokproject, get my source code, then execute grokproject.  This is so
> that the bin, develop-eggs, etc, and parts directories are created.
>
> See:
> https://answers.launchpad.net/oship/+faq/391
>
> But my thoughts are that if the users install zc.buildout and I include
> the empty (with the exception of etc and its templates) directories then
> the user should be able to execute 'python bootstrap.py' and everything
> that is needed will be created.  This would eliminate having to answer
> no to all the questions about grokproject overwriting certain files.
>
> Does this approach make sense or am I missing something?  Say something
> like how does the admin username and password get generated if not by
> grokproject?
>
> Thanks,
> Tim
>
>
>
> --
> Timothy Cook, MSc
> Health Informatics Research & Development Services
> LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook
> Skype ID == timothy.cook
> **************************************************************
> *You may get my Public GPG key from  popular keyservers or   *
> *from this link http://timothywayne.cook.googlepages.com/home*
> **************************************************************
>
> _______________________________________________
> Grok-dev mailing list
> Grok-dev at zope.org
> http://mail.zope.org/mailman/listinfo/grok-dev
>
>