[Grok-dev] configuring grok with mod_wsgi

Graham Dumpleton graham.dumpleton at gmail.com
Thu Jan 27 04:51:23 EST 2011



On Wednesday, January 26, 2011 10:37:51 PM UTC+11, Juan A. Diaz wrote:
>
> On Wed, Jan 26, 2011 at 7:25 AM, Jan-Jaap Driessen <
> jdri... at thehealthagency.com> wrote:
>
>>
>> Just an idea: would setting the WSGIPythonHome to a virgin virtualenv
>> as described in [1] work?
>>
>> 1) http://code.google.com/p/modwsgi/wiki/VirtualEnvironments
>>
>> --
>> Jan-Jaap Driessen
>>
>
> I Tried with both WSGIPythonPath and WSGIPythonHome, but not with both at 
> the same time, and I get the same error.
>
> The directives used are.
>
> WSGIPythonHome /srv/grok/merlot/Merlot/bin
>
> and 
>
> WSGIPythonPath /srv/grok/merlot/Merlot/lib/python2.6/site-packages
>

WSGIPythonPath only relates to embedded mode anyway. You were using daemon 
mode and so the equivalent is the python-path option to WSGIDaemonProcess.

Note that WSGIPythonHome is ignored if mod_python also loaded because in 
that situation mod_python is overriding mod_wsgi and initialises the Python 
interpreter. Thus mod_wsgi could not set up the home specified in 
WSGIPythonHome.

Graham
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.zope.org/pipermail/grok-dev/attachments/20110127/a9365207/attachment.html 


More information about the Grok-dev mailing list