Go to file
Loic Rodier 0183c31146 feat
Add openshift and docker scripts
2015-03-24 20:48:38 +01:00
assets feat: Add Gitlab hook. 2015-03-20 10:57:21 +00:00
etc feat: Add unit file. 2014-11-02 20:06:07 +00:00
scripts feat 2015-03-24 20:48:38 +01:00
src feat: Add Gitlab hook. 2015-03-20 10:57:21 +00:00
.dockerignore chore: Update ignore files. 2014-09-25 12:21:13 +00:00
.gitignore chore: Update ignore files. 2014-09-25 12:21:13 +00:00
Dockerfile chore: Add sudo. 2014-11-10 16:37:42 +00:00
LICENSE Init. 2014-09-19 18:46:04 +00:00
Makefile chore: Add stop and rm task. 2014-11-10 16:37:54 +00:00
README.md feat: Add Gitlab hook. 2015-03-20 10:58:57 +00:00
test.sh feat: Add Gitlab hook. 2015-03-20 10:57:21 +00:00

webhookd

A very simple webhook server to launch shell scripts.

It can be used as a cheap alternative of Docker hub in order to build private Docker images.

Installation

Linux binaries for release 0.0.1

Download the version you need, untar, and install to your PATH.

$ wget https://github.com/ncarlier/webhookd/releases/download/v0.0.1/webhookd-linux-amd64-v0.0.1.tar.gz
$ tar xvzf webhookd-linux-amd64-v0.0.1.tar.gz
$ ./webhookd

Usage

Create your own scripts template in the scripts directory.

Respect the following structure:

/scripts
|--> /bitbucket
  |--> /echo.sh
  |--> /build.sh
|--> /github
|--> /docker

The directory name right under the scripts directory defined the hookname.

For now, supported hooks are:

  • GitHub
  • Gitlab
  • Bitbucket
  • Docker Hub

The scripts under the hook directory defined the actions.

The action script take parameters. These parameters are extract from the payload of the hook. For instance the GitHub hook extract the repository URL and name. Then pass them by parameter to the action script.

Check the scripts directory for samples.

Once the action script created, you can trigger the webhook :

$ curl -H "Content-Type: application/json" \
    --data @payload.json \
    http://localhost:8080/<hookname>/<action>

The action script's output is collected and sent by email or by HTTP request.

The HTTP notification need some configuration:

Note that the HTTP notification is compatible with Mailgun API.

As the smtp notification:

  • APP_NOTIFIER=smtp
  • APP_SMTP_NOTIFIER_HOST=localhost:25