Skip to content

GitLab

  • Menu
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
  • #594

Closed
Open
Created Mar 26, 2012 by Administrator@rootOwner

Possibility to configure the context root

Created by: Prevole

In my company, we have some policy that force us to install gitlab behind a reverse proxy. We have not the possibility all the time to configure a virtual host with a proper DNS name.

We usually share multiple services behind the same reverse proxy and therefore it is not possible to use / for the context root of gitlab. What we want to do is the possibility to configure the reverse proxy to redirect /gitlab/** to the gitlab application.

After some experimentation, I cannot reach the goal to configure the reverse proxy with a fully functional gitlab. The best I successfully done is to get the gitlab home page on /gitlab but the links to the assets remains on /.

Maybe this is just a matter of configuration that I missed?

Assignee
Assign to
Time tracking