Thanks for the help. I eventually figured out how to use subdomains properly and the issue went away, but I really appreciate your thoughts on this one. It showed me an interesting part of TG that I have not yet been exposed to.
On Jul 19, 8:47 pm, Damjan <[email protected]> wrote: > > I installed a version of TG2 on Webfaction. I can have a number of > > installations there, and can have URLs redirected to each > > application. So I can have something like this: > > >http://mysite.webfactional.com/http://mysite.webfactional.com/sitea/h... > > > Each of those URLs will go to a different install of TG2. However, > > unless I install TG2 at the root URL, it doesn't behave correctly - > > the CSS doesn't load for example. I feel like I should be able to do > > one of the following: > > > a) Configure my webfaction account so it "hides" the /sitea or /siteb > > from the URL when requests are passed to TG2. > > b) Configure TG2 so it expects that its root URL comes with a /sitea > > and automatically adds it where required. > > > Any guidance on how to approach this would be appreciated. > > Are you proxy-ing? > You probably need a SCRIPT_NAME fix WSGI middleware like this : > > def proxy_fix(app, prefix=''): > def wsgi_app(env, start_response): > env['SCRIPT_NAME'] = prefix + env.get('SCRIPT_NAME', '') > return app(env, start_response) > return wsgi_app --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
