2009/7/9 cubsfanintampa <[email protected]>: > > Looks like I can use WSGIDaemonProcess / WSGIProcessGroup in each > virtual host and use a different python path. Faboosh.
Yes. It does mean that your applications are running in separate processes, but that is actually preferred somewhat over embedded mode anyway. Even if embedded mode, you can control Python module search path by explicitly working with sys.path in the WSGI script file. For further details on this and Python virtual environments, see: http://code.google.com/p/modwsgi/wiki/VirtualEnvironments Graham > -aj > > On Jul 8, 12:11 pm, aj <[email protected]> wrote: >> Hello, >> >> I have multiple WSGI applications running in a virtual host >> environment. mod_wsgi complains when I try to put WSGIPythonPath in a >> VirtualHost. This then means that my applications are forced to share >> a common path. Not ideal. >> >> Is there a different way to do this? >> >> Thanks, >> -aj > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
