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
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
> 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
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
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
5 matches
Mail list logo