You could still connect to the same database from both sites but distinct the content that should *not* be shared using a site_id. For stuff like that the django.contrib.sites framework should be quite useful :-)
http://www.djangoproject.com/documentation/sites/ - Horst On Sat, May 17, 2008 at 3:41 PM, Greg Lindstrom <[EMAIL PROTECTED]> wrote: > I am ready to deploy my first Django site on the web and am looking at > starting another. Are there any collective thoughts on whether I > should add the new app to my existing Django project or start an > entire new project? I don't want to get site data mixed together, but > I will have a number of common tables and methods ("Person", and > "Address" come to mind). I figure I could have different entries for > each site in my urls.py file and then simply install what I would need > for a particular site. I have not figured out how to handle the > "models" and "Views" files. > > Is it simply better to have separate projects? > > Thanks, > --greg > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
