Thank you for replies :-)
I forgot to mention important thing:
Those website modules will probably be run on separate hosts (they can
be put on different hosts or virtual hosts, but still use the same
database)
.. so one point in "What is common between them": "global
configuration (database uri, debug level, i18n, session etc.)" may be
misleading.
My current code layout is:
|-- my_django_projects
|-- foo_common
`-- foo_employees
`-- foo_mainwebsite
`-- foo_monitoring
In foo_common I put general settings, which are imported and can be
overwritten in specific project. foo_common contains also applications
that are used among all the projects. What I don't like is that models
definitions are spread all over the tree and using south migrations is
sensitive to human errors, like forgetting to set some migration
dependency. Second thing is that I need to run test separately for all
projects, or write some script/runner that will run all tests at one
go.
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-us...@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=.
