Skip to content

GitLab

  • Menu
    • Projects Groups Snippets
      Help
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #6269

Closed
Open
Created 11 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

Links in Wiki pages are missing relative_url_root

Closed

Links in Wiki pages are missing relative_url_root

Created by: Hocsi

I installed gitlab to a relative url (/gitlab/), not to the root. Everything works fine, except the links in the wiki. i created 2 pages: http://server/gitlab/user/newtestproj/wikis/home http://server/gitlab/user/newtestproj/wikis/masik

home page contains this link link to other page

the created link inside Wiki is this: http://server/user/newtestproj/wikis/masik the correct would be: http://server/gitlab/user/newtestproj/wikis/masik

All of these were executed:

Note that four settings need to be changed for this to work.

#1) In your application.rb file: config.relative_url_root = "/gitlab"
#2) In your gitlab.yml file: relative_url_root: /gitlab
#3) In your unicorn.rb: ENV['RAILS_RELATIVE_URL_ROOT'] = "/gitlab"
#4) In ../gitlab-shell/config.yml: gitlab_url: "http://127.0.0.1/gitlab"
# To update the path, run: sudo -u git -H bundle exec rake assets:precompile RAILS_ENV=production
#
config.relative_url_root = "/gitlab"

gitlab version: GitLab 6.5.1 GitLab Shell 1.8.0 GitLab API v3 Ruby 1.9.3p194 Rails 4.0.2

Linked issues
...

    Related merge requests

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: yms9654

      I have a same problem. Anyone help?

      By Administrator on 2014-02-17T08:05:19 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: Hocsi

      gitlab source is now maintaned at gitlab, not here. There is a merge request to fix this issue, i hope it will be fixed soon

      By Administrator on 2014-02-17T15:53:15 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: Razer6

      @Hocsi Which MR do you mean? Is it already merged?

      By Administrator on 2014-03-23T10:55:47 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: Hocsi

      https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/23

      i think this is the fix, and still in open status

      By Administrator on 2014-04-17T07:30:55 (imported from GitLab project)

    • Administrator
      Administrator @root · 10 years ago
      Owner

      Created by: Razer6

      Fixed in GitLab 7.0

      By Administrator on 2014-06-21T10:25:28 (imported from GitLab project)

    • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
    Please register or sign in to reply
    0 Assignees
    Assign to
    Milestone
    No milestone
    None
    None
    Time tracking
    Due date
    None
    None
    0
    Labels
    None
    Assign labels
    • No matching results
    • Manage project labels
    Confidentiality
    Not confidential

    You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

    Lock issue
    Unlocked
    participants
    Reference:

    Menu

    Projects Groups Snippets
    Help