[Grok-dev] Grok deployment story unclear and weird

[Graham Dumpleton]

On May 17, 4:07 am, Laurence Rowe <l... at lrowe.co.uk> wrote:
> Andreas Jung wrote:
> > Hi there,
>
> > I am currently totally clueless and confused about the
> > deployment story with Grok apps.
>
> > As developer I can create my sandbox using grokproject and implement
> > my_weird_package based on the generated skeleton. Ok, the application
> > is working - now I want to package and distribute my_weird_package.
> > What is the suggested approach for doing this?
>
> > As a Grok user I want to setup a new Grok server and install
> > my_weird_package
> > (possibly together with other Grok apps within the Grok instance). As an
> > experienced
> > Grok user I would use grokproject for creating an empty instance and install
> > my_weird_package in some way (in which way?). As a newbie Grok user I would
> > expect 'easy_install my_weird_package' to produce a running Grok instance!?
>
> > So what is the way doing it the right way - for the Grok developer/package
> > and the Grok user?
>
> As someone who has never used grok, but would like to be able to install
> grok-built applications, I'd feel most comfortable if those applications
>   were 'standard' wsgi components, just like the other wsgi applications
> I already run (trac, paste, repoze and one day plone). These most likely
> run under apachemod_wsgi. There is a tutorial here,http://grok.zope.org/documentation/tutorial/installing-and-setting-up...
>
> As far as I can tell, the only drawback to using mod_wsgi compared to
> proxying is that there is no way to provide session affinity. Useful
> when you want the zodb cache to be relevant.

There possibly is a way of providing session affinity. First off, use
daemon mode with a single process. Obviously all requests come back to
the same process so no actual need for it.

Or, use daemon mode but define multiple daemon process groups of a
single process rather than one group with multiple processes. You can
then use a couple of different ways to control which of those
processes requests go to.

This has been discussed a little on the mod_wsgi list before, but no
one has ever explained a concrete need enough to propose example
configuration and/or code of what to do.

If interested, specify what mechanism you are using to create stick
sessions.

Graham