[Grok-dev] Grok deployment story unclear and weird
lists at zopyx.com
Sat May 16 14:10:51 EDT 2009
On Sat, May 16, 2009 at 20:07, 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
> > my_weird_package in some way (in which way?). As a newbie Grok user I
> > expect 'easy_install my_weird_package' to produce a running Grok
> > So what is the way doing it the right way - for the Grok
> > 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 apache mod_wsgi. There is a tutorial here,
> 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.
(Un)fortunately I don't care much about WSGI :-)
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Grok-dev