python - Dealing with legacy django project in new localized projects -
i right in situation plan internationalization of django project contains legacy code. old project has different applications have strong dependency each other, hard separate them. looking @ time left impossible @ all.
the main requirements internationalization are:
- having separate projects each country
- each country later have different templates
- each country introduce new features other countries may want use well
- the main old codebase still maintained , should work new features/changes country projects
do have ideas/setups deal old code , starting new projects dependency old code , new features? start discussion this.
start decoupling components possible, , convert legacy code (portable) apps if not case already, , legacy code should not live under main project tree.
any new features should documented , decoupled apps or generic libraries themselves, if override/interact/depend or monkeypatch legacy code. want of project live outside of main project itself, , installable via pip if 3rd party apps.
the main project tree should not more project main project templates, urls.py, settings.py, configuration/deployment templates , fabfile, , core apps customized.
every localized customization should either "customization" apps themselves, or small tweaks main project (that should made in reproducible way via fab, or provider of choice)
needless say, if every team can commit core project, git/hg workflow essential, , use central ci server test suite.
Comments
Post a Comment