On Mar 24, 2011, at 10:35 AM, Anthony wrote: > On Thursday, March 24, 2011 12:51:56 PM UTC-4, Martin.Mulone wrote: > Yes but not in the application folder. The importance is to be distributed > with the application.
I think you two might be talking at cross purposes here. It goes in applications/myapp/ > > With both systesms, you can put a routes.py file in the application folder, > but at least with the older system, for that to work, you also need a > routes_app entry in the main routes.py file -- is that what you're saying you > don't want? In other words, you want no dependency on any central routes.py > file? Perhaps Jonathan can verify, but I think that may be possible with the > new system (i.e., having a routes.py file in your app folder without having a > routes.py file in the web2py root folder). > Both versions of routing work the same way, in principle. You need a base (root) routes.py so that the router can figure out the application (otherwise it wouldn't know which app-specific routes.py to use). The rest of the routing information can be in each applications root folder. The new router's syntax makes it pretty easy to have all the routing in the base routes.py, though, since each app can simply have its own routing dict.
