Il giorno 13/set/2010, alle ore 14.07, Italo Maia ha scritto: > Folks, i've got, like, GREAT NEWS! I managed to get uwsgi+cherokee working, > but only if i start uwsgi myself, from commando line. The weirdest thing is > that the same command, in a different port, where uwsgi running from cherokee > (it is in my Interpreter Source) gives me an:
Uhm, i am sure that i have indirectly suggested you to do this on my first email :) For example i never let cherokee spawn my application servers, as i use other systems (mainly upstart and init.d). > > uWSGI Error > wsgi application not found > > Could it mean the problem is cherokee related? Maybe a bug? Maybe i > misconfigured something? i bet for all of the three ;) I suggest you to look at this: http://projects.unbit.it/uwsgi/wiki/Example You will get a lot of ideas to choose what is the best way to deploy your app, the way you have configured uWSGI is a bit "verbose"... uWSGI is "sysadmin friendly", so there is no one-fit-for-all configuration way. It is all about taste ... Be sure that you are using the latest uWSGI version (0.9.6.1) as it includes lot of usability fixes (uwsgi --version) Experiment with the embedded HTTP server (simply add --http :<port> to the commandline) and when you are satisfied (and when you are more confident with concepts like PYTHONPATH, virtualenv and chdir) , come back to Cherokee for going into production. uWSGI and Cherokee are both "stable" and used in a lot of production environment. Recently they have had some interoperation problem, (they both evolve super-fast) but they will all be fixed :) -- Roberto De Ioris http://unbit.it JID: [email protected] _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
