Re: 2 projects based on the same codebase

[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 had a lot of appeal but I 
> quickly ran into issues with the limited ability for customization
> and the codebases began to diverge quickly.
> 
> Until you can get to the stage where you can factor out the common parts (not 
> always easy) into reusable apps  I would second the suggestion
> for separate projects. It seems like needless duplication (which it is to 
> some extent) but you easily avoid compatibility issues and then
> both projects are free to take whatever path works best.
> 
> Regards,
> 
> Stuart MacKay
> Lisbon, Portugal
> 

Hi Stuart,

thanks for link and the advise.
I've since split the code into 2 projects and so far, so good :)

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.

Re: 2 projects based on the same codebase

[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 
with the limited ability for customization and the codebases began to 
diverge quickly.


Until you can get to the stage where you can factor out the common parts 
(not always easy) into reusable apps  I would second the suggestion for 
separate projects. It seems like needless duplication (which it is to 
some extent) but you easily avoid compatibility issues and then both 
projects are free to take whatever path works best.


Regards,

Stuart MacKay
Lisbon, Portugal


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


Hi,

thanks for the info.
I will use a seperate repository for the 2nd project.

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.

Re: 2 projects based on the same codebase

[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 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
> 

Hi,

thanks for the info.
I will use a seperate repository for the 2nd project.

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.

Re: 2 projects based on the same codebase

[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 virtualenv
> and "git clone" the codebase. The new project might slightly differ in the
> futur.
>
>
Clone the codebase into a new repository for the new team. Deploy from this
repository to your server, so each team has their own repository deployed
into their own virtualenv.

Then if either side modifies the common code, you can git push/git pull the
changes across between the two root repositories.

You could also consider using git submodules to refer to the "master" copy
of the calltracking module in the second team repository.

Malcolm

-- 
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.

Re: 2 projects based on the same codebase

[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 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 
Sender: django-users@googlegroups.com
Date: Thu, 09 Jun 2011 09:06:34 
To: 
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.