Re: [web2py] Re: routes for subdomain

2010-02-17 Thread Jonathan Lundell
On Feb 17, 2010, at 9:57 AM, Thadeus Burgess wrote: > Thank you everyone! Finally. > > Wikus van de Merew your a genius. > > The following routes does it, and if you try to access > example.com/dashboard you get a 404. This is a good solution in your case because it's easy to specify the other

Re: [web2py] Re: routes for subdomain

2010-02-17 Thread Thadeus Burgess
Thank you everyone! Finally. Wikus van de Merew your a genius. The following routes does it, and if you try to access example.com/dashboard you get a 404. The only change I needed to make was to wildcard the GET/POST at the end. routes_in = ( ('.*:/favicon.ico', '/init/static/favicon.i

Re: [web2py] Re: routes for subdomain

2010-02-17 Thread Jonathan Lundell
On Feb 16, 2010, at 10:38 PM, Thadeus Burgess wrote: > example.com/controllerA/function1 -> /init/controllerA/function1 > example.com/controllerA/function2 -> /init/controllerA/function2 > example.com/controllerB/function1 -> /init/controllerB/function1 > example.com/controllerB/function2 -> /init

Re: [web2py] Re: routes for subdomain

2010-02-17 Thread Jonathan Lundell
On Feb 17, 2010, at 5:38 AM, Wikus van de Merwe wrote: > To get what you want you could use this two rules for routes_in: > ('.*:https?://domain\.com:get /([a-z]+)/(.*)', r'/init/public/\1/\2') > ('.*:https?://([a-z]+)\.domain\.com:get /(.*)', r'/init/\1/\2') > > See the full doctest example: htt

Re: [web2py] Re: routes for subdomain

2010-02-16 Thread Thadeus Burgess
example.com/controllerA/function1 -> /init/controllerA/function1 example.com/controllerA/function2 -> /init/controllerA/function2 example.com/controllerB/function1 -> /init/controllerB/function1 example.com/controllerB/function2 -> /init/controllerB/function2 example.com/$anything -> /init/defaultC

Re: [web2py] Re: routes for subdomain

2010-02-16 Thread Jonathan Lundell
On Feb 16, 2010, at 9:31 PM, Thadeus Burgess wrote: > Ok I have spent way to long on this, I can't get any configuration of > routes/mod_rewrite to rewrite the hostname. I think Massimo is right: you don't have any reason to rewrite the hostname. > > > -Thadeus > > > > > > On Tue, Feb 16,

Re: [web2py] Re: routes for subdomain

2010-02-16 Thread Thadeus Burgess
Ok I have spent way to long on this, I can't get any configuration of routes/mod_rewrite to rewrite the hostname. -Thadeus On Tue, Feb 16, 2010 at 10:51 PM, mdipierro wrote: > No you just need routes in to rewrite the hostname. Routesout just > need to delete dashboard from path. > > On Feb

Re: [web2py] Re: routes for subdomain

2010-02-16 Thread Jonathan Lundell
On Feb 16, 2010, at 4:25 PM, Thadeus Burgess wrote: > Thanks. It is not working like expected. It is now going to > /init/default/index. You might try experimenting with the doctest in routes.example.py (copy it and main to your routes.py unless it's already there). Going to the default locati

Re: [web2py] Re: routes for subdomain

2010-02-16 Thread Thadeus Burgess
Thanks. It is not working like expected. It is now going to /init/default/index. ('.*:https://dashboard.example.com:.* /(?P.*)', '/init/dashboard/\g'), -Thadeus On Tue, Feb 16, 2010 at 6:08 PM, Jonathan Lundell wrote: > On Feb 16, 2010, at 3:37 PM, Thadeus Burgess wrote: > >> By the way. >>

Re: [web2py] Re: routes for subdomain

2010-02-16 Thread Jonathan Lundell
On Feb 16, 2010, at 3:37 PM, Thadeus Burgess wrote: > By the way. > > routes_in containing > > ('.*:https://dashboard.example.com:GET /(?.*)', > '/init/dashboard/\g'), (?P... -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this g

Re: [web2py] Re: routes for subdomain

2010-02-16 Thread Thadeus Burgess
I can't find any apache rewrite rules that work in this manner. Basically i am just trying to get dashboard.example.com to internally rewrite web2py's URL scheme so that it looks at /init/dashboard but the user is still staring at dashboard.example.com in their browser. This means web2py routes_o

Re: [web2py] Re: routes for subdomain

2010-02-16 Thread Thadeus Burgess
Can I do it for just one $c then, that is all I need. Every other controller will continue to function normally, this is only a special case controller. -Thadeus On Tue, Feb 16, 2010 at 4:35 PM, mdipierro wrote: > This cannot be done with routes (at least not unless you list all > options fo