为开发服务器设置 GIT
Setting up GIT for development server
目前我们有以下 situation/problem:
我们的开发人员在本地工作
开发人员将他的更改推送到 git 服务器上的存储库（到目前为止一切正常，因为在 GitLab 上我已经设置了 ssh-key 和这个人可以 clone/pull/push )
在 开发服务器 上，我需要从 git 中提取这个 问题开始。
我们有 1 个开发服务器，有 >20 个网站，据我所知有 20 个用户 我需要放入 git 看到我们计划为所有人使用它并且 为每个用户分别创建一个 ssh-key，以便能够有权访问提取对存储库所做的更改）
以上内容对于我们的实时服务器来说基本上是一样的。
我不知道如何处理这个问题，是否有一种集中的方式可以让我简单地在服务器级别授予访问权限以拉取更改？我已经看了大约 1.5 个月了，可能看错了。
补充：我们有大约 14 台服务器 运行，就是这样。
Deploy keys
Deploy keys allow read-only access to multiple projects with a single SSH key.
This is really useful for cloning repositories to your Continuous Integration (CI) server. By using deploy keys, you don't have to setup a dummy user account.
If you are a project master or owner, you can add a deploy key in the project settings under the section 'Deploy Keys'. Press the 'New Deploy Key' button and upload a public SSH key. After this, the machine that uses the corresponding private key has read-only access to the project.
You can't add the same deploy key twice with the 'New Deploy Key' option. If you want to add the same key to another project, please enable it in the list that says 'Deploy keys from projects available to you'. All the deploy keys of all the projects you have access to are available. This project access can happen through being a direct member of the project, or through a group. See def accessible_deploy_keys in app/models/user.rb for more information.
Deploy keys can be shared between projects, you just need to add them to each project.
目前我们有以下 situation/problem:
我们的开发人员在本地工作
开发人员将他的更改推送到 git 服务器上的存储库（到目前为止一切正常，因为在 GitLab 上我已经设置了 ssh-key 和这个人可以 clone/pull/push )
在 开发服务器 上，我需要从 git 中提取这个 问题开始。
我们有 1 个开发服务器，有 >20 个网站，据我所知有 20 个用户 我需要放入 git 看到我们计划为所有人使用它并且 为每个用户分别创建一个 ssh-key，以便能够有权访问提取对存储库所做的更改）
以上内容对于我们的实时服务器来说基本上是一样的。
我不知道如何处理这个问题，是否有一种集中的方式可以让我简单地在服务器级别授予访问权限以拉取更改？我已经看了大约 1.5 个月了，可能看错了。
补充：我们有大约 14 台服务器 运行，就是这样。
Deploy keys
Deploy keys allow read-only access to multiple projects with a single SSH key.
This is really useful for cloning repositories to your Continuous Integration (CI) server. By using deploy keys, you don't have to setup a dummy user account.
If you are a project master or owner, you can add a deploy key in the project settings under the section 'Deploy Keys'. Press the 'New Deploy Key' button and upload a public SSH key. After this, the machine that uses the corresponding private key has read-only access to the project.
You can't add the same deploy key twice with the 'New Deploy Key' option. If you want to add the same key to another project, please enable it in the list that says 'Deploy keys from projects available to you'. All the deploy keys of all the projects you have access to are available. This project access can happen through being a direct member of the project, or through a group. See def accessible_deploy_keys in app/models/user.rb for more information.
Deploy keys can be shared between projects, you just need to add them to each project.