At a basic level, I agree that 1) app routing should be controlled at the
app level and 2) routes.py should be "on" by default. But I think there are
some complexities such as what to do when upgrading web2py (overwrite and
edited routes file?).
On Jul 28, 2011, at 10:57 AM, Wikus van de Merwe wrote:
> Hmmm... So this means that app-specific routes are not so useful as I
> thought. I thought I would be able
> to get away without the "web2py/routes.py" having all rules defined per
> application. In other words, I was
> expecting the defa
Hmmm... So this means that app-specific routes are not so useful as I
thought. I thought I would be able
to get away without the "web2py/routes.py" having all rules defined per
application. In other words, I was
expecting the default_router to be the default when there is no
"web2py/routes.py".
On Jul 28, 2011, at 9:30 AM, Wikus van de Merwe wrote:
> I want to use app-specific routes to make my application more portable. Let's
> assume that there
> is no "web2py/routes.py" file and my application name is "init". Now I
> created the "routes.py" file
> in "web2py/applications/init/" dire
4 matches
Mail list logo
