[Grok-dev] Github Grok Installs and runs but no web server

[lozinski]

Here are my instructions for installing grok from github. 

http://blogory.org/installing-grok

Grok Installs fine and the following all work:

bin/tests

bin/grokpy

bin/interactive_debug_prompt

But there is no paster command.  How do I start a web server?

What does grokpy do?

Regards

Chris

[lozinski]

 On Python2.7 and python3.3.

Hurrah!

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?

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:

https://raw.github.com/zopefoundation/groktoolkit/master/grok.cfg

Which extends ztk.cfg
https://raw.githubusercontent.com/zopefoundation/groktoolkit/master/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. 

Comments on my plan would be most appreciated.  Does anyone want to install this work?

So that brings me to the issue of the website.  What can we do to 

make it run faster and be able to edit it?

Regards

Chris

[Jan-Wijbrand Kolman]

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:
>
> https://raw.github.com/zopefoundation/groktoolkit/master/grok.cfg
>
>
> Which extends ztk.cfg
> https://raw.githubusercontent.com/zopefoundation/groktoolkit/master/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.

regards, jw




_______________________________________________
Grok-dev mailing list
Grok...@zope.org
https://mail.zope.org/mailman/listinfo/grok-dev

[lozinski]

On Mar 29, 2016, at 3:08 PM, Jan-Wijbrand Kolman <janwi...@gmail.com> wrote:

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.

Great to get a response on these issues. Thank you for the explanation.  Makes sense to me. 

So paster is part of grokproject or grok.install.  

On Mar 29, 2016, at 3:11 PM, Jan-Wijbrand Kolman <janwi...@gmail.com> wrote:

The first thing I thought of was the package name: it moves "install"
under the namespace "grok" where the grok package wasn't really
intendeed to be a namespace as such. I'm not exactly sure about the
implications of that.

Understood.  The reason I did not want to use the grokproject name is that this is a much simpler install.  

I am open to renaming it anything that people want.  grocore.install?

On Mar 29, 2016, at 3:03 PM, Jan-Wijbrand Kolman <janwi...@gmail.com> wrote:

What I think would be a good step forward is to have a static Grok
website served from readthedocs.org or perhaps even from pythonhosted.or

Another idea would be to move it to a Docker Container, there are multiple places that provide free hosting.  

And then we can have multiple versions on the web. 

What I really really want to do is get grok.zope.org responding quickly and have a recent release/date on the home page.  

Another idea is to release grok.install as a Docker container.  Then it is a trivial install.  And lots of free hosting.

Regards

Chris