Doug Grainger wrote: > if it's at the root, then to get to the page, i do "http://server/"; and > go directly to the application. i'd prefer to have it be at > "http://server/application/";, though, because the web server that i'm > installing it on has some other stuff on it that i don't want to > preempt. i may be able to do this with virtualhosts, but i'm not > certain.
I'm not exactly sure what you are asking about here. Is your problem that attempts to refer to a url within the application do not work correctly? If so a reference to "/login" sends the user to http://server/login instead of http://server/application/login If that is your problem the turbogears.url function is your solution. It takes a relative path (and an optional keyword list of GET parameters) and returns a full path adjusted for your app. This is configured through the 'server.webpath' variable. More information on turbogears.url here: http://docs.turbogears.org/1.0/GettingStarted/URLs More info on server.webpath here: http://docs.turbogears.org/1.0/Configuration If that is not your problem, I think we might need more info to find a solution. -Adam --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
