Re: 2 projects based on the same codebase

2011-06-15 Thread Benedict Verheyen
On 14/06/2011 17:24, Stuart MacKay wrote: > Benedict, > > One solution I tried was project franchising, > http://www.huyng.com/archives/franchising-running-multiple-sites-from-one-django-codebase-2/394/ > The idea was to have a core site that was > customized for different deployments. The idea

Re: 2 projects based on the same codebase

2011-06-14 Thread Stuart MacKay
Benedict, One solution I tried was project franchising, http://www.huyng.com/archives/franchising-running-multiple-sites-from-one-django-codebase-2/394/ The idea was to have a core site that was customized for different deployments. The idea had a lot of appeal but I quickly ran into issues

Re: 2 projects based on the same codebase

2011-06-09 Thread Benedict Verheyen
> 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

Re: 2 projects based on the same codebase

2011-06-09 Thread Malcolm Box
On 9 June 2011 08:06, Benedict Verheyen wrote: > > 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

Re: 2 projects based on the same codebase

2011-06-09 Thread delegbede
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