> > I'm definitely confused with this routing scheme. > > There's the base routes.py (which is usually ignored due to file > name). > Note sure what you mean -- if you have a /web2py/routes.py file, it will not be ignored. web2py comes with two example files, routes.parameter_example.py and routes.pattern_example.py -- of course they are ignored, as they are intended only as examples (as the filenames suggest).
> Inside this file there are 3 examples (routes_app, routes_in > and routes_out). So, assuming you change the name of the file > routes.py and restart your server, it will use routes_app (and will it > ignore routes_in and _out?). > Yes, but it will only ignore routes_in/routes_out if the incoming request does not match anything in routes_app. Importantly, though, everything in that file is just an example -- you're supposed to customize it to suit your particular routing needs. Don't just use it as is. > If I comment out routes_app in that file, > I should be picking up my patterns_in and patterns_out, but how would > it then know the top level (app) routing? > Not sure what you mean. If you don't have any routes_app (which would tell web2py to look for and use the routes.py file in the application folder when the incoming request matches a particular application), it will simply use routes_in/routes_out for all rewriting (across all applications). Anthony >
