Hi Petr, To be very honest, I dont know whether not flushing the cache might cause trouble here. I just chipped in with what little i knew :).
You could check the dev/prodn log to get a better idea of whats going on and where things get stuck. You could also disable subdomains temporarily and make sure it IS indeed a subdomain problem in the first place. But most likely, the logs will be your best friends here. You will be able to trace the problem there the best. Do let us know what you find there. And ill chip in what I can if I can :). On Apr 4, 3:23 pm, Petr Bobek <[email protected]> wrote: > Thx Ram, > > my production server ishttp://rails.mysite.com > > so the example should behttp://newband.rails.mysite.com => tld_size 2 > should be fine. > > Could it be the problem, that I didnt flush the cache? > Or is there another problem? > > Thx Petr > > Ram wrote: > > newband.mysite.net > > > if thats the URL u want, then tld_size should be 1. > > > newband.localhost:3000 > > > if thats the URL you're developing with, then tld_size should be 0. > > > tld_size = (number of dots in URL) - 1 (to put it crudely) > > -- > Posted viahttp://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
