What you need in my opinion is just one django project with multiple settings files (for each domain).
Regards, Aidas Bendoraitis [aka Archatas] On 2/21/07, Sundial Services <[EMAIL PROTECTED]> wrote: > > I would like to find references to "best practices" regarding the > design of a major site with these characteristics: > > (1) The site will support multiple URLs, which appear visually to be > entirely separate sites but which will share much of the same > implementation. The "site" module obviously provides the basic > functionality here... that's a given. > > (2) Each site will offer much the same functionality, that is to say, > the same apps such as shopping-cart, messaging and inventory. But > once again, each site is visually and functionally distinct. > > My particular interest here is: how the internal directory-structure > (as seen by the developer, not the end-user URIs) and settings can be > most-efficiently set up to maximize code-reuse (cohesion) while > minimizing (or better yet, eliminating) coupling between the sites. > > I'm no stranger to Django. > > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
