I would like to run multiple instances of a single wsgi application and map
those instances to different URLs on the same virtual server. Is that
possible? How do you do it? I tried this:
WSGIDaemonProcess app1
WSGIApplicationGroup app1
WSGIProcessGroup app1
WSGIScriptAlias /app1
That works. Thanks!
--
You received this message because you are subscribed to the Google Groups
modwsgi group.
To view this discussion on the web visit
https://groups.google.com/d/msg/modwsgi/-/88aBYDato8sJ.
To post to this group, send email to modwsgi@googlegroups.com.
To unsubscribe from
I'm still confused about something: The configuration above gives me
multiple Python sub-interpreters all running in the same unix process
(presumably the main Apache process?) But what I really want (I think) is
multiple pythons each running in their own process so that they can run in
SLSIA pretty much. This happens to me when I call subprocess.popen from
within a wsgi script with mod_wsgi running in daemon mode. It doesn't seem
to matter what the subprocess actually does (I use 'whoami' for testing).
It's a very weird error because it is intermittent but not random.
BTW, I get the exact same result on Linux.
--
You received this message because you are subscribed to the Google Groups
modwsgi group.
To view this discussion on the web visit
https://groups.google.com/d/msg/modwsgi/-/NoRmhODnADAJ.
To post to this group, send email to modwsgi@googlegroups.com.
More info: it turns out that what is failing is the call to os.fork(). The
system call itself succeeds, but every other time the child process
terminates with the error in the subject line.
--
You received this message because you are subscribed to the Google Groups
modwsgi group.
To view
I've dug into this some more, and this issue seems to be quite a rabbit
hole. The TL;DR version seems to be that calling fork() from a process that
has threads is a Really Bad Idea (tm) and cannot be reasonably expected to
work reliably.
If anyone wants details let me know.
--
You received
I'm trying to implement a limit on the size of uploaded files which depends
on a user's status, i.e. a user who pays gets to upload larger files than
one who doesn't. I want to check the size of the upload BEFORE reading the
data because I don't want to read 27 gigabytes only to find that this
No, the problem is that the entire file is (apparently) read by modwsgi
before the application code is run at all.
--
You received this message because you are subscribed to the Google Groups
modwsgi group.
To view this discussion on the web visit
Wow, that really sucks. It does indeed appear to be the case that the
server is doing the Right Thing and it's the browser that's screwing this
up. Bummer. I guess it's time to break out the client-side Javascript
filefrobber object :-(
Thanks, Graham!
--
You received this message because
10 matches
Mail list logo
