Subdirectory Support in gitlab-git-http-server or nginx configuration

I use Gitlab 8.0.1 (installed manually from source) using subdirectory myhost.com/gitlab, which worked perfectly before Gitlab 8.x. I've also used the separate Gitlab CI service with multi-runner without any problems.

In Gitlab itself everything works fine, but when using the new built-in CI service (didn't migrate from the old CI and started from scratch), the multi-runner is now not able to clone the repositories.

Cloning repository...
Cloning into 'builds/69d6f323/0/gitlab/myname/myproject'...
remote: Not Found
fatal: repository 'https://gitlab-ci-token:b93dcf5d1baf416406efbd4244b5c5@myhost.com/gitlab/myname/myproject.git/' not found

I think the new gitlab-git-http-server is not able to serve the repositories when using a subdirectory on the url. He tries to find $repoRoot/gitlab/myname/myproject.git which obviously doesn't exist. Only $repoRoot/myname/myproject.git exists. Clone over HTTPS doesn't work on my machine either, same error there.

So I've tried to rewrite the url in nginx, but then following error occures:

Cloning repository...
Cloning into 'builds/69d6f323/0/gitlab/myname/myproject'...
remote: Not Found: /myname/myproject.git/info/refs
fatal: repository 'https://gitlab-ci-token:b93dcf5d1baf416406efbd4244b5c5@myhost.com/gitlab/myname/myproject.git/' not found

maybe my rewrite is wrong?

# remove the leading /gitlab from url
rewrite ^/gitlab(.*)$ $1;

It'd be much easier if the new http service also supports subdirectory configurations.

Just Migrated to 8.0.2

git clone https://keep-it.fr/gitlab/docker/MariaDB.git
Cloning into 'MariaDB'...
remote: Not Found
fatal: repository 'https://keep-it.fr/gitlab/docker/MariaDB.git/' not found

I had the same problem. I noticed the gitlab http server is looking in the wrong repo folder because it joins the repo root with the URL path.

As a temporary workaround you can make a small change in /home/git/gitlab-git-http-server/githandler.go which seems to be working for me.

Add "regexp" to the imports.

Find the line:

repoPath := path.Join(h.repoRoot, strings.TrimSuffix(r.URL.Path, g.suffix))

and replace it with:

relPathRegex, _ := regexp.Compile("your_subdir_path/")
urlPathNoRel := relPathRegex.ReplaceAllString(r.URL.Path, "")
repoPath := path.Join(h.repoRoot, strings.TrimSuffix(urlPathNoRel, g.suffix))

Save the file, run sudo -u git -H make and restart the gitlab service.

Thanks for the fix !

I made a quick one to rebuild the sameersbn/docker-gitlab docker image i am using.

How could we get the relative root from the gitlab config ? Maybe a -relativeRoot option ?

Should we open/move this issue on gitlab-org/gitlab-git-http-server ?

mentioned in issue gitlab-git-http-server#10 (closed)

I submitted a merge request to add relative URL root support to gitlab-git-http-server (see gitlab-git-http-server!3 (closed) ). If this merge request hits the master branch, you would have to add the option -relativeURLRoot <your-prefix> in the gitlab-git-http-servercommand line option in /etc/default/gitlab.

If the development team would accept this solution, I would enjoy document the setup in the various file in the gitlab-org/gitlab-ce project.

mentioned in merge request gitlab-git-http-server!3 (closed)

Hi there,

I ended up with @rvanmil solution. Thank you. Redirecting with nginx did simply not work for me. But if you have your GitLab under /git, you have to tweak the code just a bit. I ended up with:

relPathRegex, _ := regexp.Compile("/git/")
urlPathNoRel := relPathRegex.ReplaceAllString(r.URL.Path, "/")
repoPath := path.Join(h.repoRoot, strings.TrimSuffix(urlPathNoRel, g.suffix))

I am leaving this here for future reference and the wish that relative paths may be supported in the future. That was pain.

Thank you, 73

Hi @marcel.ryser.ch,

First of all, thank you for raising an issue to help improve the GitLab product. We're sorry about this, but this particular issue has gone unnoticed for quite some time. To establish order in the GitLab-CE Issue Tracker, we must ensure that every issue is correctly labelled and triaged, to get the proper attention.

This issue will be closed, as it meets the following criteria:

• No activity in the past 4 months
• Unlabelled
• Unassigned
• It's not associated with a particular milestone

We'd like to ask you to help us out and determine whether this issue should be reopened.

If this issue is reporting a bug, please can you attempt to reproduce on the latest version of GitLab or GitLab.com, to help us to understand whether the bug still needs our attention.

If this issue is proposing a new feature, please can you verify whether the feature proposal is still relevant.

Thanks for your help

Status changed to closed

Added ~761915 label

mentioned in merge request !14785