Hello Graham,
Graham Dumpleton wrote:
>
> On Oct 29, 7:00 pm, Leho Kraav <[email protected]> wrote:
>
>> hi all wsgi gurus
>>
>> my goal was to get several isolated trac no-site-packages virtualenvs
>> running under mod_wsgi: 0.11 virtualenv for bunch of live projets,
>> 0.12-dev1 for project dev1 and 0.12-dev2 for project dev2. but i am
>> somewhat unclear regarding ApplicationGroups and ProcessGroups - some
>> setup guides did it one way, some the other. so i also seem to have a
>> mix in my config file. what about having both dev1 and dev2 both in
>> ApplicationGroup %{SERVER}%, should they be in separate AG, or does
>> separate PGs take care of that? perhaps someone could tell me if
>> there's something to be fixed here:
>>
>
> For Trac, due to limitations in Python wrappers for subversion, you
> must use:
>
> WSGIApplicationGroup %{GLOBAL}
>
> So, if using subversion you don't have a choice and if need separation
> must use daemon process groups instead.
>
Speaking of that, I'm not sure if you've seen that someone recently
reported the "instance.__dict__ not accessible in restricted mode" issue
with mod_wsgi 2.5, despite his use of WSGIApplicationGroup %{GLOBAL}
(see http://trac.edgewall.org/ticket/3371#comment:73).
As we don't see the whole configuration he was using, it might be that
the WSGIApplicationGroup directive was wrongly applied. OTOH, he
reported success with a similar setup using mod_python, so it's a bit
troubling. Are you aware of situations where that RuntimeError could
still occur with mod_wsgi 2.5 even when WSGIApplicationGroup %{GLOBAL}
is used?
-- Christian
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Users" 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/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---
