你为什么需要Gitosis或Gitolite？ [英] Why do you need Gitosis or Gitolite?
问题描述
对不起，我的无知 - 但是Gitosis或Gitolite有什么收获。
Sorry for my ignorance - but what is the gain of having either Gitosis or Gitolite.
我有一台Synology NAS服务器正在运行，但是我可以不创建裸NAS上的任何文件夹？
I have a Synology NAS server running, but could I not just create a "bare" on any folder on the NAS?
问候
推荐答案
看到我的答案关于验证和授权：一个DVCS（分布式VCS）没有。
See my answer about "authentication and authorization": a DVCS (Distributed VCS) has none.
- Gitosis已死（过时，未维护）。 。
- Gitosis is dead (obsolete, not maintained).
- Gitolite is about authorization, not authentication.
您将使用ssh或httpd将授权机制与身份验证机制耦合。
You will couple that authorization mechanism with authentication ones, using ssh or httpd.
但是，它必须是一个与某些形式的sshd或httpd兼容的认证系统。
为什么？因为访问服务器的git客户端只知道这两种协议说话。 （好吧，git：//协议是未经验证的，file：//并不适用于本次讨论，所以我们忽略了这些）。
However, it has to be an authentication system that is compatible with sshd or httpd in some form.
Why? Because the git client accessing the server only knows those 2 protocols to "speak git". (Well, the git:// protocol is unauthenticated, and file:// doesn't really apply to this discussion, so we're ignoring those).
例如，假设您有一个基于LDAP的身份验证系统。
可以让apache使用它来验证用户，所以当用户使用 http访问一个git url时， //sitaram:password@git.example.com/repo ，它是进行实际认证的LDAP。
For example, let's say you have an LDAP-based authentication system somewhere.
It is possible to make apache use that to authenticate users, so when a user accesses a git url using http://sitaram:password@git.example.com/repo, it is LDAP that does the actual authentication.
这篇关于你为什么需要Gitosis或Gitolite？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
