Add a new configuration option, custom_hooks_dir. When this is set, we
will look for global custom hooks in:
    <custom_hooks_dir>/{pre-receive,update,post-receive}.d/*

When this is not set, default to <REPO_PATH>/hooks.

Dirk Posselt authored 8 years ago and Sean McGivern committed 8 years ago

This commit adds the option of having another set of global custom hooks
along with the already supported repository local custom hooks.

The repository local custom hook is executed first (if available). If
successful, execution continues with the global custom hook (if available).
This way, local custom hooks get priority over global custom hooks.

Global custom hooks can be enabled by placing an executable file into the
"custom_hooks" directory within gitlab-shell (create if it does not exist,
yet).

`make update-redis` will clone the library and adjust the paths properly

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Something like gitlab-shell.log-20140626.gz will not be caught by the
original pattern match since '.' is taken as a literal character.

This prevents concurrent modification of authorized_keys file

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Ignore gzipped logs as well.