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

Closed
Open
Created Oct 06, 2012 by Administrator@rootOwner

put local-code in gitolite-admin repo

Created by: apmorton

when you run gitlab and gitolite on two separate servers, like I am doing now, you have to share some directories between them for all functionality to work

one of these folders is the gitolite hooks folder

the gitolite manual suggests adding a 'local-code' folder to the gitolite-admin repo to be able to manage hooks remotely.

if this was done, it would help decouple gitlab and gitolite, which makes it easier for more advanced configurations to be completed.

this also provides a cleaner solution for #1639 with the post-receive patch

Assignee
Assign to
Time tracking