On Wed, Feb 4, 2009 at 9:11 AM, Ales Zoulek <ales.zou...@gmail.com> wrote:
> > As I undrestood it is that it's infact *used* on Apache. > That's why the django project is on "/peergw" - Apache, but "/" - dev > server. > > That the "/peergw/" is needed to reach the code running on Apache implies the Location block for the Django portion of the Apache site is <Location "/peergw/">, but implies nothing about django.root. I don't see anything in what the original poster said that implies django.root is being used, rather the question implies it is not being used. If the PythonOption django.root were used, and set to /peergw, then this prefix would be invisible to the app's code, as per the docs "Django will automatically strip the <django.root value> string from the front of any URLs before matching them against yourURLConf patterns." Thus the app's url config is portable -- it does not need to be changed when changing the prefix for the site, so the exact same code can be used when running under Apache or the dev server. I assumed that is what the original poster is looking for, though the question is not entirely clear, and it was asking to achieve this in a way backwards from what is normally done (adding the prefix when running under the dev server as opposed to stripping it when running under Apache). Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
