Even experts have basic questions sometimes... :)
So, I am starting on a project that is different from my usual Django work. In brief, it will be a single database with three separate sites in front of it.
The underlying Django implementation will have a significant number of apps in common, with some apps separate. They will share some view functions, while having separate urlconfs, templates, static files, etc.
The sites framework is obviously designed for this, but I'm wondering how to structure the actual code:
-- One directory and VCS repository, with separate "project" packages for each one within it, and different manage.py's (renamed) for each one. The shared apps and the separate apps would all live at the same level, so it would be something like:
root/
shared-app-1/
shared-app-2/
site-a-app/
site-b-app/
site-c-app/
site-a-manage.py
site-a/
url.py
site-b-manage.py/
... etc.
-- Independent VCS repositories, with the shared apps as submodules or something like that.
Thoughts?
--
-- Christophe Pettus
xof@thebuild.com
--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/9546A517-78CC-4207-9845-9778E638E017%40thebuild.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment