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

Closed
Open
Created May 19, 2015 by Administrator@rootOwner

Running GitLab alongside Node?

Created by: ghost

My primary app is built using Node, supports WebSockets, etc., but I would like to run GitLab on the same server within a subdirectory. I've put off making this issue for more than a day, trying to figure something out on my own, but apparently the omnibus package doesn't support (and has no plans to support) setting the relative_url_root. So now I've uninstalled the omnibus package and am going with the custom installation, and running into some issues along the way, probably due the previous omnibus installation.

Surely running GitLab on the same server and domain as other services is a really common use-case, so how is everyone else doing it? I can't seem to find anything on this specifically. Maybe I'm not looking in the right places.

After the custom installation (for relative_url_root support), the approach I was planning on going with was either A) use node-http-proxy and point to unicorn's port 8080 for http://localhost/gitlab or B) use a different port for the node app and update GitLab's nginx configuration to act as a reverse proxy to that port for any URLs outside of http://localhost/gitlab.

Assignee
Assign to
Time tracking