Re: 2 projects based on the same codebase

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

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

> 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

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

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

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