[英]How to structure source control repository for a platform with iOS, Android, Web apps and Java backend?
There is a back-end service written in Java and there is a web app, Android app and iOS app that serve the service. 有一个用Java编写的后端服务,有一个Web应用程序,Android应用程序和iOS应用程序为服务提供服务。
Any typical SaaS product will fit this bill. 任何典型的SaaS产品都符合此法案。
I am looking for best practices and guidelines so that I don't have to move code around and maximize the code to be modular. 我正在寻找最佳实践和指南,以便我不必移动代码并最大化代码模块化。
Do you put code for each app in separate source control repositories or do they live in a single repository? 您是否将每个应用程序的代码放在单独的源代码控制存储库中,还是将它们存放在单个存储库中?
What is the usual practice? 通常的做法是什么?
Do you put code for each app in separate source control repositories or do they live in a single repository? 您是否将每个应用程序的代码放在单独的源代码控制存储库中,还是将它们存放在单个存储库中?
What is the usual practice? 通常的做法是什么?
They should be in a single repository each. 它们应该分别位于一个存储库中。
You can use submodules
for this purpose. 您可以使用submodules
来实现此目的。
Submodule is a project inside project. 子模块是项目内的项目。 The benefits of submodules is that it will allow you to use shared resources for the IOS & Anndroid by sharing the same folders. 子模块的好处是它允许您通过共享相同的文件夹来为IOS和Anndroid使用共享资源。
Git-Tools-Submodules Git的-工具-子模块
git-tip-of-week-git-submodules 混帐梢的周混帐子模块
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.