[Grok-dev] Grok Installs and Runs Correctly
janwijbrand at gmail.com
Tue Mar 29 15:08:47 CEST 2016
On 11/03/16 08:35, lozinski wrote:
> On Python2.7 and python3.3.
> Surprisingly grok did not include paster or daemon. So I added them in.
> That was the hard part. Now that I have it running, making the
> following changes should be a lot easier. So what is next?
What do you mean? The grok *package* didn't depend on paster or
anything? I guess that was deliberate as in principle developers should
be able to choose the wsgi-server themselves. For that the grokproject*
tool was about bringing all kinds of ingredients together to setup a
work web application.
> Basically I want to create a simple version of grokproject so that those
> who are interested can start using grok. The original grokproject is
> really nice, it asks you all kinds of questions, and fills in the
> values. But that is a lot of work to upgrade it. I just want a simple
> installation where the defaults are chosen for you, and one can edit the
> values. I want to leave the original grokproject alone, in case anyone
> wants to upgrade it. So how will I do this?
> First I will fork the grok github repository. I will call it
> zopache.grokproject. Merge these changes into it. I want to copy in
> the sample app template from grok.project. And then update INSTALL.txt
> and README.txt. Maybe taking parts from grokproject.
> I also want to move the cfg files.
> buildout.cfg extends grok.cfg:
> Which extends ztk.cfg
> I want to move those two files into zopache.grokproject
> That will be easier to understand, and not at risk of those urls changing
> during production.
Of course you can inline thise *.cfg files into your own project if you
want to. We do that for our own (non-public) projects too. It is "just"
a matter of maintaining those files. In this case that's not so hard as
the ecosystem doesn't change all that often currently.
More information about the Grok-dev