问题描述
我的服务器已经在 TCP 端口 80 和 443 上运行了 IIS.我想通过 Internet 为我的所有团队成员提供一个集中的推/拉"Git 存储库.
My server already runs IIS on TCP ports 80 and 443. I want to make a centralized "push/pull" Git repository available to all my team members over the Internet.
所以我应该使用 HTTP 或 HTTPS.
So I should use HTTP or HTTPS.
但是我无法使用 Apache,因为 IIS 已经在端口 80 和 443 上连接了侦听套接字!有没有办法通过 IIS 发布 Git 存储库?Git 使用 WebDAV 吗?
But I cannot use Apache because of IIS already hooking up listening sockets on ports 80 and 443! Is there any way to publish a Git repository over IIS? Does Git use WebDAV?
更新. Git HTTP 安装似乎是只读的.这很可悲.我打算在构建服务器上保留稳定分支,并在推送时使用钩子重新部署.除了在该分支上使用 SVN 之外,还有人看到其他解决方法吗?
Update. It seems that Git HTTP installation is read-only. That's sad. I intended to keep the stable branch on a build server and redeploy using a hook on push. Does anyone see a workaround besides using SVN for that branch?
推荐答案
Bonobo Git Server
GitAspx - 作者:Jeremy Skinner
GitAspx - By Jeremy Skinner
https://github.com/JeremySkinner/git-dot-aspx/
https://github.com/JeremySkinner/git-dot-aspx/downloads
安装说明
https://www.jeremyskinner.co.uk/2010/10/19/gitaspx-0-3-available/
Git Web
WebGitNET
https://github.com/otac0n/WebGitNet
或者......(非 IIS,但强烈推荐,免费和开源)
Alternatively ... (non-IIS, but highly recommend, free and open-source)
Gitea(Gogs 的分支):https://gitea.io
Gitea (fork of Gogs): https://gitea.io
Gogs:https://gogs.io
SCM Manager 允许您轻松地为 Git、Hg 和 SVN 设置修订控制端点相同的托管过程.支持 HTTP/HTTPS 以及内置用户身份验证.
SCM Manager allows you to easily set up revision control endpoints for Git, Hg, and SVN under the same hosting process. HTTP/HTTPS is supported along with built-in user authentication.
https://www.scm-manager.org
https://bitbucket.org/sdorra/scm-manager/
这篇关于如何在 IIS 上设置 Git 裸 HTTP 可用存储库的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持!