Question

I’ve built a Django site that will live at the root when it’s live. Right now it’s functioning perfectly at the IP address. For testing purposes, the client has pointed a proxy url at it, but the url has /folder/path in it, so none of the URL patterns match. I put (/folder/path)? into all the url patterns so they now respond, but all of the links are broken because I’m using the {% url %} tag and while the url patterns will match the optional path, they don’t include it in that tag.

Clearly I can just hard-code /folder/path into all of my urls (well, into all of the url includes) until testing is complete, but is there a better way to do this?

Answer 1

You manage this when you deploy your application, by correctly setting the WSGIScriptAlias in your Apache configuration (assuming you’re using mod_wsgi, which you should be doing). This is passed on to Django, which then automatically prefixes all URL reverse lookups with the correct value. You shouldn’t need to do any manual mucking about with prefixes.