blocks|key|1171988|text|当然，有一个具有访问控制的自托管git存储库是可能的。通常，我们要做的是在服务器机器上创建一个名为git的帐户，将该帐户的外壳设置为git-shell，这是一个仅供git使用的有限外壳，然后将每个授权用户的公钥放在git-+user的..ssh/git_git文件中。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1171989|http://blog.commonthread.com/2008/4/14/setting-up-a-git-server掌握了大部分实际细节。|1171990|entityMap|0|LINK|mutability|MUTABLE|url|http://blog.commonthread.com/2008/4/14/setting-up-a-git-server^0|1D|3|1U|9|2Z|3|3F|3|3J|3|0|0|1Q|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@]|D|@$9|11|A|12|1|13]]|E|$]]|$1|H|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

It's certainly possible to have a self-hosted git repository with access control. Typically what one would do is create a account named <code>git</code> on the server machine, set the shell of that account to <code>git-shell</code>, which is a limited shell designed for use by git only, and then put the public keys for each authorized user in the <code>git</code>-user's .ssh/authorized_keys file.

<a href="http://blog.commonthread.com/2008/4/14/setting-up-a-git-server" rel="noreferrer">http://blog.commonthread.com/2008/4/14/setting-up-a-git-server</a> has most of the rest of the actual details.

blocks|key|1116633|text|我们使用的是神推和拉出的吉托。见湿疣。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1116634|entityMap|0|LINK|mutability|MUTABLE|url|http://swik.net/gitosis^0|G|2|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

We're using gitosis where devs push to and pull from. See <a href="http://swik.net/gitosis" rel="nofollow noreferrer">gitosis</a>.

blocks|key|1171916|text|这就是我所用的技巧。为每个人设置账户和密钥是一件很麻烦的事，但这只需要做一次。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1171917|更重要的是，如果您正确地列出了内容，您可以在git://+http://whatever或http://whatever上拥有一个只读存储库，在git%2Bssh://任何地方都可以使用可写存储库。|offset|length|1171918|编辑:+gitosis看起来确实很整洁，尽管您可能希望在任何地方的某个阶段为您的所有开发人员设置个人帐户。|1171919|entityMap|0|LINK|mutability|MUTABLE|url|http://whatever/|1^0|0|T|F|0|19|F|1|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@$D|S|E|T|1|U]|$D|V|E|W|1|X]]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|O]]]]

That's pretty much the technique I use. It's a hassle to set up accounts and keys for everyone, but that only needs to be done once.

As a bonus if you lay things out right you can have a read-only repository available at git://whatever or <a href="http://whatever" rel="nofollow noreferrer">http://whatever</a> and your writable repository at git+ssh://whatever.

EDIT: gitosis does look pretty neat, although you might want to have individual accounts for all your developers at some stage anywhere.

blocks|key|1172091|text|与此同时，世界发生了很大变化，我认为http://gitblit.com/是目前最好的解决方案之一(取决于您的需求)：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1172092|只可使用HTTPS轻松设置。|unordered-list-item|1172093|集成在LDAP公司中。|1172094|允许定义组/团队，以及对存储库的细粒度访问控制。|1172095|是开源的，所以安装起来很便宜(与Github和其他人相比)|1172096|因此，如果您不想为每个团队都提供一个新的服务器，这确实是一种选择。我们喜欢它！|1172097|entityMap|0|LINK|mutability|MUTABLE|url|http://gitblit.com/^0|I|J|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|F|7|10|8|@]|9|@]|C|$]]|$1|G|3|H|5|F|7|11|8|@]|9|@]|C|$]]|$1|I|3|J|5|F|7|12|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|13|8|@]|9|@]|C|$]]|$1|M|3|N|5|6|7|14|8|@]|9|@]|C|$]]|$1|O|3|-4|5|6|7|15|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

The world has changed a lot in the meanwhile, and I think that <a href="http://gitblit.com/" rel="nofollow">http://gitblit.com/</a> is currently one of the best solutions (depending on your requirements):

<ul>
<li>Can be setup easily with HTTPS only.</li>
<li>Integrates in the company LDAP.</li>
<li>Allows to define groups / teams, and fine graned access control to the repositories.</li>
<li>Is open source, so cheap to install (compared to Github and others)</li>
</ul>

So if you don't want to have a new server for each and every team, this is really an option. We like it!

blocks|key|1116668|text|如果你想自己运行，有很多git管理GUI。例如，立功很好。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1116669|为了您的身份验证需要，这主要取决于您。您可能很难让ssh遵守您喜欢的auth技术(上次这样做时，我修改了ssh以读取LDAP中的密钥)。|1116670|我敢肯定，网络界面可以做你想做的任何事情。不过，我可能会把它打开在网络内部。|1116671|entityMap|0|LINK|mutability|MUTABLE|url|http://gitorious.org/^0|O|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

There are lots of git management GUIs out there if you want to run it yourself. <a href="http://gitorious.org/" rel="nofollow noreferrer">gitorious</a> is nice, for example.

For your authentication needs, that's mostly up to you. You may have a hard time having ssh honor your preferred auth technique (last time I did anything like that, I modified ssh to read keys out of LDAP).

The web interface could do whatever you'd like, I'm sure. I'd probably just leave it open on the inside of the network, though.

blocks|key|2696674|text|我很惊讶，没有人提到开源项目gogs：http://gogs.io，它基本上提供了与gitlab相同的功能(不包括Wiki、代码评论、代码片段)，但系统资源最少(占用较少)，非常适合在Raspberry+Pi中运行。安装和维护也更简单。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2696675|entityMap|0|LINK|mutability|MUTABLE|url|http://gogs.io/^0|J|E|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Im quite suprised nobody mentioned the open-source project gogs: <a href="http://gogs.io" rel="nofollow">http://gogs.io</a> which basically offers the same what gitlab does (without including Wiki, Code Review, Code Snippets), but with minimal system resources(low footprint), being perfect to run in a Raspberry Pi for example. Installation and maintenance is also way simpler.

blocks|key|1172067|text|我会有点担心为您的版本控制系统建议git。Visual+是微软的产品，而git则处于另一个极端，在Windows上几乎不起作用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|BOLD|entityRanges|data|1172068|TortoiseGit是git的一个Windows接口，现在可以使用了。这是我最初的反应，因为我觉得对你的源代码控制系统有一个GUI访问对大多数Windows开发人员来说是非常重要的。|1172069|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/tortoisegit/^0|H|3|L|7|10|3|0|0|B|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]|$9|T|A|U|B|D]|$9|V|A|W|B|D]]|E|@]|F|$]]|$1|G|3|H|5|6|7|X|8|@]|E|@$9|Y|A|Z|1|10]]|F|$]]|$1|I|3|-4|5|6|7|11|8|@]|E|@]|F|$]]]|J|$K|$5|L|M|N|F|$O|P]]]]

I'd be a bit concerned about suggesting <code>git</code> for your version control system. Visual Source Safe is about as Microsoft of a product as one can get, while git is on the other extreme and barely functions on Windows. 

<a href="http://code.google.com/p/tortoisegit/" rel="nofollow noreferrer">TortoiseGit</a>, a Windows interface to git, is now available. This tempers my original response, as I feel having a GUI access to your source-control system is very important for the majority of Windows developers.

I am presenting Git to a 10 man programming team who currently use Visual Source Safe. 

They need to host their Git server inside the company. Windows or Linux. Directory authentication is Novell eDirectory.

They need some granular security on who can push to the central server.

From: 

<a href="https://stackoverflow.com/questions/923130/what-type-of-git-server-do-you-use-or-how-do-you-use-git">https://stackoverflow.com/questions/923130/what-type-of-git-server-do-you-use-or-how-do-you-use-git</a>

Maybe a workflow could be:

<ul>
<li>Setup 10 users on the server. </li>
<li>Setup a common directory on the servers filesystem that the 10 users have write access to</li>
<li>Push files to the server via SSH eg git push dave@test.com:user1/project.git</li>
<li>But then I need that the keys are installed on the server</li>
</ul>

Question: Does anyone use a workflow like this successfully in a company. What works? This is starting to feel like most people use Git with GitHub etc.. 

[Edit]: Please see <a href="https://stackoverflow.com/questions/1768486/how-not-to-scare-programmers-using-visual-source-safe">Choosing a source control system: logical next steps after VSS</a> Maybe Git isn't the right fit for this team.

Git in a company - hosting own server

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在向一个10人编程团队介绍Git，该团队目前正在使用Visual。他们需要在公司内部托管他们的Git服务器。Windows或Linux。目录身份验证是Novell eDirectory。他们需要一些关于谁可以推送到中央服务器的细粒度安全。发自：也许工作流可以是：在服务器上安装10个用户。在服务器文件系统上设置一个公共目录，10个用户都可以对其进行写入访问。通过SSH将文件推送到服务器，例如gi

问在托管自己的服务器的公司中使用Git
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在托管自己的服务器的公司中使用GitEN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在托管自己的服务器的公司中使用Git
EN