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

Closed
Open
Created May 27, 2013 by Administrator@rootOwner

Clarification needed. Why is web server necessary for Gitlab?

Created by: safar

Can someone please explain to me, why do we use web servers such as nginx or Apache for Gitlab 5.2 when the same thing can be achieved using only Puma app server run on port 80?

Is there some performance benefit or is the main reason the possibility to run multiple web pages on port 80 alongside Gitlab?

Also I have managed to get Gitlab 5.2 to work with Apache without Passenger. Is there a reason why all other instructions I came across used Passenger along side unicorn for previous versions of Gitlab? I mean, both passenger and unicorn are both app servers on their own, just don't see the point of running them together.

Or maybe I've got this whole thing wrong in my head...

Assignee
Assign to
Time tracking