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

Closed
Open
Created Feb 16, 2012 by Administrator@rootOwner

Note I think should be added to some FAQ

Created by: andrewfenn

Sorry for reporting this as an issue however it's not apparent to me how to contribute documentation.

I have come across a problem which I feel others may come across in the future.

If you are having problems creating projects in GitLab and you have hooks in gitolite then you must make sure that the user you are running gitlab under has access to the /home/git/.gitolite/hooks/common directory because it makes a symlink to the hooks you have put there in every git repository.

The best way to avoid this is to simply run gitlab under the same user that runs gitolite although I am unaware if this presents a security hazard or not?

Assignee
Assign to
Time tracking