I think everything could be accomplished by creating a separate settings.py file for each site, and pointing to them in your virtual hosts. By installing your apps outside the project dirs, but still in the PYTHON_PATH, you can refer to the same app dirs in all settings files. The only problem I can see is if you specify a different DB in each settings.py, you'll need to create the same admin accounts in each.
-Robin On Apr 24, 7:22 am, Nick Tidey <[EMAIL PROTECTED]> wrote: > Hello all. > > I'm creating a CMS/e-commerce Django project for a client which will > ultimately be used to handle content for three different domains. > > In terms of sharing of resources: > - content will not be shared between sites > - public templates will differ between sites > - the administration interface is the same for all sites (a customised > version of the Django administration interface) > - each site will use the same group of Django apps > - the client would like administration user accounts to be shared > across all sites > - I would like each site to at least use a separate set of tables; > preferably separate databases > > I'm new to Django and I've read up on Django's site framework; read > about various Apache configurations, searched for information on > multiple database connections in Django, etc. There's a lot to take > in. > > I'm hoping someone can suggest a way to handle this. > > I'm looking to host the sites on a WebFaction shared account. > > Thanks > Nick --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
