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

Closed
Open
Created Jun 21, 2013 by Administrator@rootOwner

puma is starting in development mode

Created by: kirantpatil

I have Upgraded GitLab to v5.3.stable.

puma.rb is configured to run on production mode.

puma.rb file snippet below

-# Set the environment in which the rack's app will run. -# -# The default is “development”. -# environment = :production

Here is what I see on terminal,

kiran@patchbee:/home/git/gitlab$ sudo service gitlab start rm: cannot remove `/home/git/gitlab/tmp/sockets/gitlab.socket': No such file or directory Puma 2.0.1 starting...

  • Min threads: 0, max threads: 16
  • Environment: development
  • Listening on unix:///home/git/gitlab/tmp/sockets/gitlab.socket GitLab service started
Assignee
Assign to
Time tracking