The following was taken from [1].
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - -
Web2Py
web2py does not work well on multiple application environment so you
have to use it as the only WSGI application of the uWSGI server.
Use this wsgi script (look at the chdir call where you have to specify
the app path):
import os
os.chdir("full_path_of_your_web2py_app")
import gluon.main
application = gluon.main.wsgibase
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - - - - -
Why do you say that does not work well in environments with multiple
applications?
I'm rewriting an application web2py. The "old application" is in
production (Cherokee + fastcgi) and the "new application" (beta
version) with Cherokee + uwsgi. They work well for both applications.
I tried to change the "old application" from fastcgi to uwsgi. The
first application that run from the browser works well (whether new or
old), but the other fails when trying to access the database,
obviously this is the same database.
[1] http://projects.unbit.it/uwsgi/wiki/Example
