On 13/12/2014, at 8:12 AM, Joonas Lehtolahti <[email protected]> wrote:
> On Fri, 12 Dec 2014 22:55:42 +0200, Jennifer Mehl <[email protected]> > wrote: > > ... > >> WSGIDaemonProcess chroot user=daemon group=daemon processes=2 threads=25 >> chroot=/var/chroot python-path=/var/chroot/var/www/transfergateway > > ... > >> I believe my issue now is relating to the PythonPath directive and access >> to the project/Python my chroot, but am unsure how to resolve. >> >> I'm kind of stuck-- so I appreciate the help! >> >> --Jennifer >> > > Just a thought from an outsider: since the Python interpreter is running > inside chroot, perhaps the python-path option needs to point to a path local > to the root, that is, it shouldn't contain /var/chroot. Yes, that is correct. General Apache configuration should use /var/chroot as well as WSGIScriptAlias. But anything that would be applied when handling a request shouldn't have /var/chroot as it is being used by the application inside of the chroot. So I would agree that should probably be: WSGIDaemonProcess chroot user=daemon group=daemon processes=2 threads=25 \ chroot=/var/chroot python-path=/var/www/transfergateway Thanks Joonas, you beat me to it. :-) 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.
