#1213: incomplete support for changing server.webpath
------------------------+---------------------------------------------------
Reporter:  nludban     |        Owner:  anonymous
Type: defect | Status: new Priority: normal | Milestone: Component: unassigned | Version: 1.0b2 Severity: normal | Resolution: Keywords: | ------------------------+---------------------------------------------------
Comment (by nludban):

Recommended setup instructions...

Configure Apache (httpd.conf) to proxy everything under /mytgproject to
the
TG server:
{{{
<Location /mytgproject>
    ProxyPass http://localhost:8080/mytgproject
    ProxyPassReverse http://localhost:8080/mytgproject
    RequestHeader set CP-Location /mytgproject
</Location>
}}}

Configure TG (dev.cfg) so it knows how it's being accessed:
{{{
server.webpath = '/mytgproject'
}}}

Note that both Apache and TG agree on the application root.  Access should
work consistently whether being proxied through Apache or testing against
the CherryPy server directly.

Now use ${tg.url('/foo')} in all templates to have the server.webpath
value
prefixed to absolute (relative to the TG project) URLs.

--
Ticket URL: <http://trac.turbogears.org/turbogears/ticket/1213>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears Tickets" 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-tickets?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to