Hi Benedict, This is a mere advice. I hope someone can come up with an elegant solution pretty soon.
The two projects though similar are different and as such there is a possibility that one might get more complex than the other at a much faster rate depending on the client's need. Just go ahead and have a different repository for each and let them be independent of each other. My reason for this is that you have gone live and shouldn't take chances in trying to save time or keystrokes. If there are other solutions, I would also like to see. All the best. Regards. Sent from my BlackBerry wireless device from MTN -----Original Message----- From: Benedict Verheyen <benedict.verhe...@gmail.com> Sender: django-users@googlegroups.com Date: Thu, 09 Jun 2011 09:06:34 To: <django-users@googlegroups.com> Reply-To: django-users@googlegroups.com Subject: 2 projects based on the same codebase Hi, I developed a calltracking for our team and now, another team is interested to have their own calltracking. The best way to seem to deal with a project that is the same from the start, is to makea new virtualenv and "git clone" the codebase. The new project might slightly differ in the futur. I have a development machine where I maintain the code, then "git push" the code to a server. On the production machine, i "git pull" the code. This all works but what if the 2nd team wants slight changes, changes that my team may not want? 2 virtualenv's based on the same code might not be the best option in this case. Do I create a new repository for the code of the other project ? I feels like the best way to go ahead. However, this would mean that I need to maintain 2 projects that are and probably will remain very similar. How would i transfer code changes from 1 repository to the other? Patches? Thanks for any insight, or links to documentation that deal with this kind of setup and sorry in advance for going OT. Regards, Benedict -- 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. -- 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.
