On Jun 23, 3:48 am, Chris <[email protected]> wrote: > On Jun 10, 9:45 pm, Graham Dumpleton <[email protected]> > wrote: > > > Try using mod_wsgi instead. Much easier to set up for virtual > > environments. See: > > > http://code.google.com/p/modwsgi/wiki/IntegrationWithTrac > > http://code.google.com/p/modwsgi/wiki/VirtualEnvironments > > > Graham > > Graham > > I was able to get both Trac 0.11.7 and Trac 0.12 running, but, 0.11 is > using mod_python and 0.12 is using mod_wsgi. I'm on Windows and > couldn't get WSGIDaemonProcess to work because as you know, it doesn't > work. I had this configuration using mod_wsgi but when accessing the > Trac 0.11 sites I was informed to upgrade their Trac database. > > WSGIScriptAlias /trac12 F:/virtualenvs/trac12/Scripts/trac12.wsgi > > <Location /trac12> > WSGIApplicationGroup %{GLOBAL} > Order deny,allow > Allow from all > </Location> > > WSGIScriptAlias /trac11 F:/virtualenvs/trac11/Scripts/trac11.wsgi > > <Location /trac11> > WSGIApplicationGroup %{GLOBAL} > Order deny,allow > Allow from all > </Location>
You cant mix different virtual environments in same Python interpreter (mod_wsgi application group). If you are using third party C extension modules that only work in main Python interpreter, eg, subversion bindings, then on Windows you are out of luck as you would in that case have no choice but to use daemon mode, which as you know is only available on UNIX with Apache 2.X. Graham -- 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.
