> > Honestly I've always thought routes.py was a little mysterious and > "magical" and I don't like relying on magic for a deployed website. >
Hmm, I don't see it as any more "magical" than Apache mod_rewrite. Probably you have just misconfigured something. > So learning url-rewriting in Apache is probably the best thing to do long > term anyway. > Keep in mind that Apache will only handle rewriting of incoming requested URLs -- you will be responsible for generating the outgoing URLs (i.e., you will not be able to use the web2py URL() function to generate proper URLs). Also, if you ever switch to a different web server (e.g., Nginx), your code won't be portable. Likewise, the URLs won't be the same in development if you are using the web2py development server (and this could make things tricky if your app code is generating URLs without the aid of the URL() function). Anthony -- 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.
