Hi,
It might be relevant:
https://groups.google.com/d/topic/web2py/cZTV9YRqWGk
https://groups.google.com/forum/#!topic/web2py/mmOWQfOUw98
Yet what Massimo suggested about updating routes_in and routes_out did not
work for me
(in Apache 2.4 + mod_wsgi / web2py-2.13.4-stable on kubuntu 14.04)
when I used routes.patterns.example.py as a template for routes.py and set
BASE = 'w2p' there. The routing went completely wrong way.
The supplied with web2py routes.parametric.example.py suggested another
solution that I ended up with
to allow independent php and python applications on the same apache2:
1. cp <path-to-web2py>/examples/routes.parametric.example.py
<path-to-web2py>/routes.py
2. appending path_prefix='w2p', to the BASE router there:
routers = dict(
# base router
BASE=dict(
default_application='welcome',
path_prefix='app',
),
)
3. updating VirtualHost config with
WSGIScriptAlias /w2p <path-to-web2py>/wsgihandler.py
...
AliasMatch ^/w2p/([^/]+)/static/(?:_[\d]+.[\d]+.[\d]+/)?(.*)
<path-to-web2py>/applications/$1/static/$2
...
<Location /w2p/admin>
Require ip 127.0.0.1
</Location>
...
<LocationMatch ^/w2p/([^/]+)/appadmin>
Require ip 127.0.0.1
</Location>
...
that seems to work for 'user applications', but some links generated in the
admin app still appear to ignore path_prefix and land on the webroot.
When I append webroot in the resulting urls with '/w2p' manually in the
browser location box they sometimes work.
Good luck,
o
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
