On 13/01/2010 21:36, Graham Dumpleton wrote:
2010/1/14 mog<[email protected]>:
Hi,
I'd like to add my code to python's path variable so I can do import
statements. From what I understand, in daemon mode I can tell mod_wsgi where
my code is using the python-path option, a bit like this:
WSGIDaemonProcess testtest.elasticmind.net processes=1 threads=5 \
display-name=test python-path=/home
Add:
WSGIProcessGroup testtest.elasticmind.net
You haven't told mod_wsgi to run that application in that daemon process group.
Note that using 'processes=1' is not recommended unless you understand
the side affects of what it does. Just drop that option if only want
one process as that is what it defaults to. The subtle difference is
that whenever 'processes' option is used, even for one process, the
'wsgi.multiprocess' flag is set True in WSGI environment. This can
prevent WSGI debuggers from working as they need guarantee that not
multiprocess.
Also suggest you use 'display-name=%{GROUP}' rather than
'display-name=test'. Calling process 'test' may be too confusing and
make it harder to spot in 'ps' listing especially since 'test' is the
name of a common UNIX utility.
Graham
Ahh right, this makes lots more sense now, thanks. I was originally
using 'display-name=%{GROUP}', but swapped it out at some point whilst
trying to get it working. It was going to get changed back to something
more sensible as soon as I'd worked out what was breaking.
Kind regards,
mog.
--
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.
