--+
+-+ project1
| +- => common
| +- config.file
| +-+ data
| +- blah
| +- wrxgl
| +...
+-+ project2
| +- => common
| +- config.file
| +-+ data
| +- blah
| +- wrxgl
| +...
+-+ project2
| +- => common
| ...
+-+ common
+- foo
+- bar
+- baz
+...
If these projects are identical except for a few files, why not setup several projects (folders in SVN) each of which only contains these differing files and an external reference to a project (folder) with all the common stuff?
Something like this:
--+
+-+ project1
| +- => common
| +- config.file
| +-+ data
| +- blah
| +- wrxgl
| +...
+-+ project2
| +- => common
| +- config.file
| +-+ data
| +- blah
| +- wrxgl
| +...
+-+ project2
| +- => common
| ...
+-+ common
+- foo
+- bar
+- baz
+...
Unless each site is significantly unique, I personally would have only had one branch with translations in resource files. My data models would have the ability to be local so when the whole thing went live there was one set of files and one database feeding the whole lot.
Perhaps I'm spoilt. I get a lot of this functionality for free with Django but gettext is pretty universal and sorting routing (et al) isn't that tough.
发布评论
评论（2）
如果这些项目除了几个文件之外都是相同的，为什么不设置几个项目（SVN 中的文件夹），每个项目只包含这些不同的文件和一个 对包含所有常见内容的项目（文件夹）的外部引用？
像这样的事情：
--+ +-+ project1 | +- => common | +- config.file | +-+ data | +- blah | +- wrxgl | +... +-+ project2 | +- => common | +- config.file | +-+ data | +- blah | +- wrxgl | +... +-+ project2 | +- => common | ... +-+ common +- foo +- bar +- baz +...If these projects are identical except for a few files, why not setup several projects (folders in SVN) each of which only contains these differing files and an external reference to a project (folder) with all the common stuff?
Something like this:
--+ +-+ project1 | +- => common | +- config.file | +-+ data | +- blah | +- wrxgl | +... +-+ project2 | +- => common | +- config.file | +-+ data | +- blah | +- wrxgl | +... +-+ project2 | +- => common | ... +-+ common +- foo +- bar +- baz +...除非每个站点都非常独特，否则我个人只会有一个在资源文件中包含翻译的分支。我的数据模型能够成为本地数据，因此当整个数据模型上线时，就会有一组文件和一个数据库来提供所有数据。
也许我被宠坏了。我通过 Django 免费获得了很多这样的功能，但是 gettext 非常通用，并且排序路由（等）并不那么困难。
Unless each site is significantly unique, I personally would have only had one branch with translations in resource files. My data models would have the ability to be local so when the whole thing went live there was one set of files and one database feeding the whole lot.
Perhaps I'm spoilt. I get a lot of this functionality for free with Django but
gettextis pretty universal and sorting routing (et al) isn't that tough.