I was wondering how I should structure my git repo(s) when dealing with native cross platform mobile apps.
我想知道在处理本地跨平台移动应用程序时，我应该如何构造我的git repo。
this is the issue: I have made a native mobile app for IOS and Android, with that comes a small backend to link to databases, written in php.
这是一个问题:我已经为IOS和Android开发了一个本地移动应用程序，它的一个小后端连接到数据库，用php编写。
what is the most efficient way to manage this project. should i make multiple repos, so i can store each fragment of the project separate. or 1 big repo with all code and project files for this cross platfom mobile app?
管理这个项目最有效的方法是什么?如果我要做多个repos，那么我可以将项目的每个片段分开存储。或1个大的回购，所有的代码和项目文件为这个跨平台移动应用程序?
2 个解决方案
#1
0
Git submodule concept designed for your needs. Main idea is that you could organise each project as git submodule of main git repo. Git submodules doc: http://git-scm.com/book/en/v2/Git-Tools-Submodules
为您的需要设计的Git子模块概念。主要的想法是，您可以组织每个项目，作为主要的git repo的git子模块。Git子文档:http://git-scm.com/book/en/v2/Git-Tools-Submodules
#2
0
If creating new and separate repositories for each 3 of them is not a problem, then I would vote for separate repositories. It would be cleaner to manage, and you will have better compartmentalization. You can share only the required codebases with the people that you want to grant access to.
如果为其中的每3个创建新的和独立的存储库不是问题，那么我将投票支持独立的存储库。它会更清洁，你会有更好的划分。您可以只与希望授予访问权限的人员共享所需的代码库。
If, however, creating separate ones cost you more money, you can go ahead and create just one repository and have 3 folders in it, one for iOS, 2nd for Android and the 3rd for your php code.
但是，如果创建单独的程序需要花费更多的钱，那么您可以继续创建一个存储库，其中有3个文件夹，一个用于iOS, 2个用于Android, 3个用于php代码。
#1
0
Git submodule concept designed for your needs. Main idea is that you could organise each project as git submodule of main git repo. Git submodules doc: http://git-scm.com/book/en/v2/Git-Tools-Submodules
为您的需要设计的Git子模块概念。主要的想法是，您可以组织每个项目，作为主要的git repo的git子模块。Git子文档:http://git-scm.com/book/en/v2/Git-Tools-Submodules
#2
0
If creating new and separate repositories for each 3 of them is not a problem, then I would vote for separate repositories. It would be cleaner to manage, and you will have better compartmentalization. You can share only the required codebases with the people that you want to grant access to.
如果为其中的每3个创建新的和独立的存储库不是问题，那么我将投票支持独立的存储库。它会更清洁，你会有更好的划分。您可以只与希望授予访问权限的人员共享所需的代码库。
If, however, creating separate ones cost you more money, you can go ahead and create just one repository and have 3 folders in it, one for iOS, 2nd for Android and the 3rd for your php code.
但是，如果创建单独的程序需要花费更多的钱，那么您可以继续创建一个存储库，其中有3个文件夹，一个用于iOS, 2个用于Android, 3个用于php代码。