It's difficult to deploy gitlab on a sub URI.

Created by: crocket

After searching for about 3 hours, I figured out that passenger was the only way to deploy gitlab on a sub URI.

I deployed gitlab on /gitlab.

It took 7 hours to figure out that I had to manually edit app/views/admin/resque/show.html.haml to configure the correct URL for resque view.

I changed /info/resque to /gitlab/info/resque in that file.

I consume an entire day just to deploy gitlab on a sub URI.

I think gitlab manual should mention about deploying on a sub URI.

Created by: rspeicher

Once you were running under Passenger, was the Resque view the only problem you encountered? Because that was recently fixed in master. So I'm curious if, other than further documentation, there was anything else stopping someone from deploying that way.

By Administrator on 2012-09-09T11:52:02 (imported from GitLab)

Created by: piffio

There is actually another problem with gitlab running on a sub URI:

Both issue and commit URL in markdown documents (using #issue an the commit hash) don't honor the sub URI. Ex. you're running under /gitlab using the markdown syntax to reference an issue will create a link to: /project/issue/ instead of /gitlab/project/issue/

This probably affects all the links generated via the markup syntax

By Administrator on 2012-09-09T15:44:31 (imported from GitLab)

Created by: perj

Merge request links (e.g. !42) and snippets (e.g. $4711) are also wrong.

By Administrator on 2012-09-13T07:00:41 (imported from GitLab)

Created by: riyad

#1950 (closed) might solve this.

By Administrator on 2012-12-06T15:32:44 (imported from GitLab)

Created by: nickbroon

Close as duplicate of Issue #1950 (closed) which has a pending pull request?

By Administrator on 2012-12-06T13:37:22 (imported from GitLab)