> What do you think?
I'm not sure I get it -- you want to automatically load a settings
file based on the subdomain? That seems a little too magic for me,
especially when you can already do this just by changing
DJANGO_SETTINGS_MODULE for each domain...
Nopes, I don't want it to magically discover it, I am just recommending splitting the settings.py generated by django-admin.py into common_settings.py and wwwexamplecom_settings.py or something, latter keeping only subdoman/domain specific ROOT_URLCONF setting. People new to django are already quite confused, and running different instances of django with slightly modified settings.py does not apprear to be comepletely safe, this will tell them exactly what to do if they want to split their application in different subdomains/domains. There is already a SITE_ID which is quite confusing.
--
Amit Upadhyay
Blog: http://www.rootshell.be/~upadhyay
+91-9867-359-701
