We're setting up both an intranet and a public site that will sit on top of the same database. The two sites will share much content, but will have different designs, different media, and different overall purposes. There won't be much in the way of truly shared views, despite the need for shared data (for example, students might enter their stories on the intranet, but stories will be displayed on the public site - data is shared, not the view).
We're debating whether to : 1) Use the Django "Sites" framework, where the whole thing is one project with two settings files and two urls files. or 2) To build them as two separate projects pointing to the same database, with a set of shared apps between them. In other words, if the main point of the "Sites" framework is for view sharing, we may not need to use it in order to deploy multiple sites on a shared database. Which approach is considered best practice? Any gotchas either way we should be aware of before deciding on an architecture? Thanks, Scot --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
