The problem: How do you best configure a Django project so that it can be deployed in a production Intranet environment where you don't "own" the domain root url, i.e. the Django project appears at http://www.mydomain.com/some/url/path/to/django/project/name (and it could change!)? However, at the same time I want to be able to run the development environment at http://127.0.0.1/ and want any maintenance overhead e.g. managing two sets of url.py files or changing any urls stored in the database (flat files).
>From researching posts and blogs, I know this is a difficult issue but was wondering whether anyone has come up with simple solutions? Richard --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
