Generally, I'd create a different app for different functionality. IE one for authentication related stuff, another for the forum, another specific to the website. It's really a matter of style though.
You can put the model definitions most anywhere. You might want to check out the sites framework: http://docs.djangoproject.com/en/dev/ref/contrib/sites/ On Oct 27, 11:46 am, zimnyx <zim...@gmail.com> wrote: > Hi! > > I got idea of three completely different, large websites, which share > the same business model and same database. > Saying "completely different", I don't mean just different look. These > websites are something like: administarion tool, user services, etc. > They are large and have completely different purpose, but the use the > same models and database. > After watching some django-related showcasts (like > this:http://www.youtube.com/watch?v=A-S0tqpPga4), I'm getting a feeling > that website != django application, and single website should be made > of many small applications. Is this django philosophy or just one way > to achieve goal? > > How would you lay out such thing? > Single project with 3 big applications (= websites) or maybe 3 > separate projects sharing same models. Which solution you would > consider in case of django? > And last question is how would you implement sharing same model > between those 3 parts? Where would you put the model definitions? > > Cheers. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
