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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
