Thanx for the reply Roberto. Yes, I can get uwsgi running with the quick start instructions with no trouble. The problem I'm having is exposing it to Cherokee. It's supposed to be really easy, but I've tried a great many combinations I've found around the web, but none have worked. That's why I asked about the --module parameter. Still, every time I browse to the URL for my Django app, I get a 404.
No one on the Cherokee list seems to have an idea of what's wrong, so I thought I'd find out if anyone here has done this successfully. Alvaro suggested I do a source build of Cherokee so I can do a trace; I've done that and have the output from it. Italo Maia suggests not configuring the information source as a local interpreter, but instead, creating a Remote Host that just points to 127.0.0.1, and the port (on mine it's 44946). I like this idea because in the future I can separate my web server from my Django app server. I've started uwsgi with the configuration Italo suggested (which is shown below) and put it into an upstart script. Does anyone on this list have a uwsgi, Django, Cherokee configuration that's working for them? Here is my Upstart script: ----------------------------------------------------- description "uWSGI server for triagedb" author "Brian Myers" start on runlevel [235] stop on runlevel [!235] respawn exec /usr/sbin/uwsgi -s 127.0.0.1:44946 -t 10 -M -p 1 -C --module triagedb_wsgi --no-orphans --pp /var/www/NurseTriage/triagedb/triagedb_app --pp /var/www/NurseTriage/triagedb --gid tarka --uid tarka _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
