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