This is similar to something we have used for one of our clients, except we used multihost.py :)
+1 for this approach On Sun, Sep 11, 2011 at 3:49 PM, Alessandro Pasotti <apaso...@gmail.com>wrote: > 2011/9/9 sjtirtha <sjtir...@gmail.com> > >> But I cannot set the SITE_ID in the settings.py right? >> Because if one user set the SITE_ID = 1, then parallel another user >> can set the SITE_ID = 2. >> Because we only have one instance. >> > > > Right, but AFAIK if you don't use threads you shouldn't have any problem. > > We have been using the middleware hack with Django 1.2.6 from more than one > year. > > The midleware run first and set settings.SITE_ID according to the current > site, something like > > http://dpaste.com/612953/ > > Currently running nginx + uwsgi but we used mod_wsgi for the last couple of > months. > > -- > Alessandro Pasotti > w3: www.itopen.it > > -- > 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. > -- 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.