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
  • #1413

Closed
Open
Created Sep 09, 2012 by Administrator@rootOwner

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.

Assignee
Assign to
Time tracking