2009/1/5 Alberto Valverde <[email protected]>:
> <Location />
> WSGIProcessGroup prod.toscawidgets.org
> </Location>
> <Location /widget/>
> WSGIProcessGroup widgetbrowser.toscawidgets.org
> </Location>
>
> WSGIScriptAlias /widget /home/www/toscawidgets/wsgi/widgetbrowser.wsgi
> WSGIScriptAlias / /home/www/toscawidgets/wsgi/twWebSite.wsgi
>
> ...
>
> Trac isn't being forced, AFAIK, to be run in the first interpreter. I've
> just added:
> WSGIApplicationGroup %{GLOBAL}
> under the "/" Location section (where trac runs at) to see if it makes a
> difference, I'll report back later today.
Doing it at '/' Location will mean it will be inherited by /widget as
well. Since the widget application is in separate daemon process that
is fine. Will actually trim usage of widget daemon process by a very
small amount as will not create an additional sub interpreter.
Normally one would use Directory to qualify process/application group,
but you have both scripts in same directory so a bit more fiddly to do
it that ways as would need to used Files directive within Directory
directive to qualify what applies to what.
Anyway, %{GLOBAL} should definitely help as svn Python wrappers known
to need it.
Graham
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en
-~----------~----~----~----~------~----~------~--~---
