jacobvosmaer

The git:// protocol requires its own daemon (which is bundled with Git) running on port 9418 https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protoco... . The standard Git daemon is unsuitable for GitLab I think because of the way it manages access control.

https://git-scm.com/book/en/v2/Git-on-the-Server-Git-Daemon

For this to work in GitLab we would need to find or write an alternative implementation of the protocol.

Sounds like a lot of work to me when we already have decent HTTP clone access.

> It would be nice to see a separate post on this process and any performance comparisons.

We (I) see gitlab-git-http-server more as a functional improvement than as a performance improvement. It is a better match for slow Git HTTP requests ('git push', 'git pull') than Unicorn+Rails.

Having said that, I am also curious about what this change means for performance and other areas. It already helped us find a performance issue in the Rails app.

https://gitlab.com/gitlab-org/gitlab-ce/issues/2341

The budget for NWO 639.073.005 is stated to be €1,500,00.00 at http://www.nwo.nl/onderzoek-en-resultaten/onderzoeksprojecte... .

You can also get paid support for GitLab from http://www.gitlab.com (disclosure: I work for GitLab.com).