On 5 feb, 13:01, Christoph Zwerschke <[email protected]> wrote: > Am 05.02.2012 16:48, schrieb Chris Lambacher: > > > Your package probably is not in the import path when you are running > > from outside the source directory. You would need to use one of the ways > > of adding it to the path. PYTHONPATH env variable is probably the > > easiest way that does not interfere with other installed things. If you > > are using completely separate virtualenv's for each project you could > > also do python setup.py develop > > You might get away with os.chdir() in your WSGI script, but python > setup.py develop/install is the proper solution. > > See > alsohttp://www.turbogears.org/1.5/docs/Deploy/NginxWsgi.html#using-a-virt... > > -- Christoph
Thanks for the tips guys! Now I have implemented an init script for uwsgi which specified the PYTHONPATH and seems to be working properly. Thanks a lot for your support and your work helping us run our site with a proper production setup! Feel free to have a look : http://vodo.net/ Next should be some performance tunning, I guess I need to post to uWSGI list. My concern is if I should run several instances of uWSGI to spread the load across them on the same server because trying to increase workers/processes to uwsgi daemons was giving some error last time I tried it. All the best! Rama -- You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en.
