Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
042cee3a
Commit
042cee3a
authored
Jun 15, 2020
by
John Cai
Committed by
Evan Read
Jun 15, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update server hooks custom_hooks_dir location
parent
c3bdd05d
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
3 deletions
+12
-3
doc/administration/server_hooks.md
doc/administration/server_hooks.md
+12
-3
No files found.
doc/administration/server_hooks.md
View file @
042cee3a
...
...
@@ -68,9 +68,18 @@ Follow the steps below to properly set up a server hook for all repositories:
`/home/git/gitlab-shell/hooks`
. For Omnibus installs the path is usually
`/opt/gitlab/embedded/service/gitlab-shell/hooks`
.
To look in a different directory for the global custom hooks,
set
`custom_hooks_dir`
in the GitLab Shell config. For
Omnibus installations, this can be set in
`gitlab.rb`
; and in source
installations, this can be set in
`gitlab-shell/config.yml`
.
set
`custom_hooks_dir`
in the Gitaly config. For Omnibus installations, this is set
in
`gitlab.rb`
. For source installations, the configuration location depends on the
GitLab version. For:
-
GitLab 13.0 and earlier, this is set in
`gitlab-shell/config.yml`
.
-
GitLab 13.1 and later, this is set in
`gitaly/config.toml`
under the
`[hooks]`
section.
NOTE:
**Note:**
The
`custom_hooks_dir`
value in
`gitlab-shell/config.yml`
is still honored in GitLab
13.
1 and later if the value in
`gitaly/config.toml`
is blank or non-existent.
1.
Create a new directory in this location. Depending on your hook, it will be
either a
`pre-receive.d`
,
`post-receive.d`
, or
`update.d`
directory.
1.
Inside this new directory, add your hook. Hooks can be
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment