Hello list,
I'd like to offer python support to my virtual hosting customers and I want
to avoid the FastCGI/flup fiasco if at all possible. Based on my limited
working knowledge of uwsgi and WSGI applications in general and butting my
head up against the uwsgi documentation here's what I've come up with so
far:
nginx.conf snippet:
location ~ \.py$ {
uwsgi_pass 127.0.0.1:3031;
include uwsgi_params;
uwsgi_param UWSGI_PYHOME /u1/www/corbe.net;
uwsgi_param UWSGI_CHDIR /u1/www/corbe.net;
}
I'm starting uwsgi with the following command line (mostly for testing this
configuration):
# ./uwsgi -s 127.0.0.1:3031 --uid 1 --gid 65534 --vhost --no-site
The stated goal here is to produce a situation where a visitor can call (for
example) /test.py. NginX will match that and pass it to uwsgi. The catch
is I don't want to do any pre-processing of my own before the user's
application gets called. Ideally I'd like uwsgi to drop right into the
user's def application(environ, start_response):
My test.py looks like this:
def application(environ, start_response):
start_response("200 OK", [("Content-Type", "text/plain")])
return ["Hello World!"]
Currently it isn't working as desired so I'm soliciting helpful advice.
Please point me in the right direction. Thanks!
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
