Thanks to Graham for his incredibly useful response and my apologies for
my slow response.

On 16/05/16, Graham Dumpleton ([email protected]) wrote:
> > I'd also like to confirm that while setting the TZ is necessary under a
> > WSGIDaemon, it is ok to run copies of the same app with the same TZ
> > but different configuration under the same WSGIDaemon but with different
> > WSGIApplicationGroup names. For instance, I might have 3 apps in the
> > Australia/Sydney TZ which are collected under the same WSGIDaemon, but
> > can each be configured to use different databases so long as they have
> > different WSGIApplicationGroup names.
> 
> Although that technically can be done, I would still recommend a
> separate mod_wsgi daemon process group per distinct hosted
> application.
> 
> This is so that you can always force:
> 
>     WSGIApplicationGroup %{GLOBAL}
> 
> for all instances of the application.
> 
> Using this will force the use of the main interpreter context in the
> respective mod_wsgi daemon process groups, which is equivalent to
> using command line Python.

Thank you for the very useful information.

...

> > When testing this setting the WSGIProcessGroup seemed to work under both
> > a <Location> and <Directory> block, which the docs suggest shouldn't happen.
> > http://modwsgi.readthedocs.io/en/develop/configuration-directives/WSGIProcessGroup.html
> > Using <Location> is good for us due to the correlation with the url end
> > point across hundreds of production apps.
> 
> There is no issue with using Location directive as the context for
> WSGIProcessGroup. In saying a context of ‘directory’, that also means
> Location directive.
> 
> The definition of what the values mean for context can be found in
> Apache documentation at:
> 
>     http://httpd.apache.org/docs/2.4/mod/directive-dict.html#Context 

Thank you very much for the Apache doc translation. 

Regards
Rory

-- 
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/modwsgi.
For more options, visit https://groups.google.com/d/optout.

Reply via email to