Doug Van Horn was right. Each website has just one settings file. So the SITE_ID should just point to a some id of the Site object (http://example.com). Set ServerAlias *.example.com in the Apache settings for all subdomains to point to the same django project.
And then in the views you can parse the URL and and get appropriate content according the subdomain. Regards, Aidas Bendoraitis [aka Archatas] On 3/1/07, Doug Van Horn <[EMAIL PROTECTED]> wrote: > > On Feb 28, 6:33 pm, Michael Cuddy <[EMAIL PROTECTED]> wrote: > > > > Any ideas? > > -- > > I would defer to those more fluent with Django, but my understanding > of the sites framework is that there should be 1 site per settings > file, and thus 1 per project or 'website'. > > With that said, I'm working on a similar concept in an application > where the subdomain.domain.tld identifies a 'Site', but not a Django > sites framework site. > > I'm using middleware to set the site model onto the session (as > determined by HTTP_HOST), and data access is driven off of that > model. That's probably not what you're looking for, though. > > Maybe someone else will post something more helpful. :-) > > Doug Van Horn > http://www.maydigital.com/ > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
