I am again running into occasional problems trying to run the trunk code
from a subfolder instead of from a root folder under apache and mod_wsgi.
Maybe my problem is compounded because I also have another web2py installed
at the root, but it seems that some of the internal web2py
functions are not working properly and are sometimes not obeying the route
specifications.
I have a subdomain set up which has web2py 1.99 installed at the root of
the domain.
WSGIScriptAlias / /opt/web-apps/web2py/wsgihandler.py
WSGIScriptAlias /trunk /opt/web-apps/w2p_trunk/web2py/wsgihandler.py
I now have my routes.py file like this:
routes_in=(('/trunk/(?P<any>.*)','/\g<any>'),)
routes_out=(('/(?P<any>.*)','/trunk/\g<any>'),)
In general, most things seem to work. The problems I am having:
1) Sometimes -- not always -- the links to tickets will link to the top
level web2py install instead of the site under "trunk"
2) I cannot use or edit (without error) any python modules added to an
application's modules folder.
"Failed to reload module: because no module named xxx.modules.test"
If I load the site using the internal rocket server there are no problems.
--
