On 08/11/2014, at 3:05 AM, Daniela Hase <[email protected]> wrote:
> If that's the case (would make sense since it's not working as expected), how > can I have different python paths for each virtual host then? You simply shouldn't be using mod_wsgi embedded mode in the first place usually. http://blog.dscpl.com.au/2012/10/why-are-you-using-embedded-mode-of.html When using mod_wsgi daemon mode it becomes a lot simpler as you can customise separately the Python module search path and even the Python virtual environment used, for each mod_wsgi daemon process group. The mechanisms available are touched on in the post: http://blog.dscpl.com.au/2014/09/python-module-search-path-and-modwsgi.html In short, use a mod_wsgi daemon process per site, using the same one across 80/443 if have both http and https access. Presuming you are using a recent mod_wsgi version and not stuck with an ancient version shipped with a Linux distribution, then use the 'python-home' option to WSGIDaemonProcess to attach that daemon process group to a specific Python virtual environment. Set the 'home' option to the project directory which should be the current working directory and which also should be searched for Python modules. Finally, use 'python-path' to set extra Python module search directories, but only if they aren't already covered by the 'python-home' option for the Python virtual environment and the 'home' directory for the project location. Graham -- 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 http://groups.google.com/group/modwsgi. For more options, visit https://groups.google.com/d/optout.
