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

Closed
Open
Created Nov 13, 2014 by Administrator@rootOwner

Explicit Paths in Configuration Files Are Problematic

Created by: u550ccer

In several of the gitlab configuration files, /home/git is explicitly referenced. However, for some systems, the users' home directories are not in /home, but mapped elsewhere. So, every time an upgrade is performed, those config files need to be updated.

The configuration files could instead use the tilde shorthand reference and eliminate this issue. So, for example in /etc/init.d/gitlab, instead of: app_root="/home/$app_user/gitlab" you could have: app_root="~$app_user/gitlab"

Assignee
Assign to
Time tracking