On Tue, Jul 22, 2008 at 2:05 PM, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote: > > > On Tue, 2008-07-22 at 10:58 -0700, Malcolm Tredinnick wrote: >> >> On Tue, 2008-07-22 at 04:40 -0400, arsyed wrote: >> > Hi - With the change in 8015: >> > >> > http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#ChangedthewayURLpathsaredetermined >> > >> > it sounds like I shouldn't need to specify the WSGIScriptAlias in the >> > URLConf file. But this doesn't work for me (setup pasted below). Does >> > this mean I should continue to prefix "/mysite" in urls.py or is there >> > a way to avoid this? >> >> The whole idea of that change is so that you don't need the site prefix >> in your urls.py file. That way you can easily move the code from >> under /mysite to /my_other_site without having to change anything. This >> makes it particularly straightforward to, for example, develop on your >> local machine without having to worry about the prefix it is deployed >> under in production. >> >> So, yes, removing the "/mysite" prefix is exactly the change required >> here. > > I mean remove this prefix from your urls.py file. Keeping the > WSGIScriptAlias intact is the way to go here. You should only need to > modify your Django applications, not your webserver-related config. > > Regards, > Malcolm > > >
It turns out my problem was in urls.py. But you're right, this change makes it much nicer when moving between my production and local setups since I can remove some cruft from my urls and settings files. Thanks for clarifying. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
