I have a question about how people relate django projects & apps (including django apps that are shared between projects) to git repositories.
We are using a gitolite setup on a central server to share repositories between developers. Right now we have two different projects, each with a corresponding git repo, which function as standalone sites. I am evolving one of the two sites to basically "merge" the two projects and include several apps from both. For now I am just leaving the repositories separate, and setting up the master project to include apps from the other project in settings.py and make sure they end up in the PYTHONPATH, which seems to work. As this stands, different apps pertain to different repos, even though I am using them all in the same project. I am not yet completely comfortable with this setup, and am wondering how people usually manage their git repositories with respect to their projects and apps, while dealing with shared apps and remaining true to DRY principles? Do you use a 1 to 1 repo-to-project relationship? Or do you have multiple projects in 1 repo? Or do you have a different directory & corresponding repo for all shared apps, and then a repo for each project and corresponding project-specific files and apps? or just 1 centralized repo for all your django projects? Something else? Just curious if there is a best way to manage this both from a project- management and a git perspective. Thanks br -- 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.
