如何在本地为开发人员搭建GIT环境，而实时数据只能在一台服务器上获取？
我们有一个场景，其中单个服务器正在运行，它从网络范围获取数据。
每个开发人员都应该在本地计算机上工作，但要处理的数据仅在服务器中可用。我怎样才能将数据复制到每个开发人员的机器中，以便一旦他们在本地机器上完成开发，开发人员就可以将其推送到服务器中的 GIT。
PS：网络跨度数据不断写入服务器（数据大小为数百GB）。
到目前为止我们已经尝试过：
因此，我们在获取数据的服务器中创建了一个 GIT 服务器。但是，一旦开发人员使用他的用户名登录，他就会在目录中创建一个新分支。这一切正常，直到另一位开发人员使用他的用户名登录服务器并切换到同一目录中的另一个分支，这将导致所有开发人员分支到新分支。这不是我们所期待的。
We have a scenario in which single server is running, which is getting data from the network span.
Every developer should work on their machine locally but the data to work on is only available in the server. how can I get the data to be replicated into each developers machine so that once they have completed development on their local machine, developers can push it to a GIT in the server.
PS: The network span data is constantly written to the server (data is in size of 100s of GB's).
What we have tried so far:
So we created a GIT server in the server we were getting the data on. But once a developer log in using his username then he creates a new branch in a directory. This works fine until another developer logs into the server with his username and switches to another branch in the same directory which will cause all the developers branch to the new one. which is not what we were expecting.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这个问题可能要转到 https://serverfault.com/ ，但是，无论如何...
GIT优势是拥有本地和远程储存库，因此，在服务器中，您应该只有“”远程存储库，并且应该在LocalMachines中克隆。
要使用该范式，或者与您要的范式一起使用，您需要007的透明度（取决于您的分发编辑 /ettc/login.defs并在此处进行更改），
您应该有不同的组，用于不同的共享项目，不同的共享项目，例如，用户“拥有所有存储库”，例如git-adm）。
使用所有先决条件，您可以与该用户一起创建所有存储库的基本文件夹：
“粘性咬合”中的最后一行，Wich允许构建组（并避免您先前所说的问题）存储库应该是类似的：
这就是：如果文件夹
/srv/git/＆lt; group＆gt;/我们为不同的组拥有，那么它将保留该组。Probabily this question should go to https://serverfault.com/, but, anyway...
The git advantage is to have local and remotre repositories, so, in the server, you should have "only" the remote repositories, and they should be cloned in localmachines.
to work with that paradigm, or with the one you are asking for, you need a umask of 007 (depending on your distribution edit /etc/login.defs and change there)
You should have diferent groups for the diferent kind of shared projects, and a user to "own all the repositories", for example, git-adm ).
With all the prerequisites, you create with that user the base folder for all the repositories:
The last line in the "sticky bite", wich allows to mantain the group (and avoid the problems you previously stated), so, in order to cerate a repository should be something like:
And thats all: if the folder
/srv/git/<group>/we owned for a diferent group, then it'll keep the group.