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

Closed
Open
Created Aug 23, 2012 by Administrator@rootOwner

hardcoded path for post-receive hook fs-exists check should not fatal gitlab:app:status

Created by: damianb

Considering that a multitude of people (including myself) frown upon the use of /home/ for serving anything out of, and instead prefer other locations within the filesystem for locating servers (such as /srv/), it should be expected that the post-receive hook may not exist there.

Throwing a fatal error when it does not exist there is useless in circumstances like my own.

A better alternative would be a warning, IMO - "We don't think this is right - check this unless you know what you're doing" would be far better than "File does not exist, return 1 and BAIL OUT"

Assignee
Assign to
Time tracking