Receive webhooks from GitLab and store the data in the database.
GitLab has the option to send webhooks for multiple events that can be used for different purposes. This package handle the receiving, validating and storing of the webhook data. After receiving it will dispatch an event that can be used to do with the data what fits your application.
You can install the package via composer:
composer require tjvb/gitlab-webhooks-receiver-for-laravel
You can publish and run the migrations with:
php artisan vendor:publish --provider="TJVB\GitLabWebhooks\GitLabWebhooksServiceProvider" --tag="migrations" php artisan migrate
Listen to the
\TJVB\GitLabWebhooks\Events\HookStored::classevent. The package store the webhook data and dispatch an event, you can listen to the HookStored event and handle it the way you want. The Laravel documentation can explain more about events and listeners.
GITLAB_WEBHOOK_SECRETenv variable (most used version is to set it in the .env file) to have the token you use for your webhook. See https://docs.gitlab.com/ee/user/project/integrations/webhooks.html#secret-token for more information.
Create a webhook in GitLab. You can create a webhook in GitLab for your project, group or system. The default url is
<application.tld>/gitlabwebhookthis can be changed in the configuration.
Optional configure the package.
Manual register the service provider.
If you disable the package discovery you need to add
\TJVB\GitLabWebhooks\GitLabWebhooksServiceProvider::class, to the providers array in config/app.php
You can publish the config file with:
php artisan vendor:publish --provider="TJVB\GitLabWebhooks\GitLabWebhooksServiceProvider" --tag="config"
The default configuration validates the
X-Gitlab-Token in the header of the webhook request. It is possible to add multiple values in the config file or disabling the middleware to stop the verification. If you need more validation for the request (as example and i.p. filter) you can add more middleware to the configuration.
We (try to) document all the changes in CHANGELOG so read it for more information.
You are very welcome to contribute, read about it in CONTRIBUTING
If you discover any security related issues, please email email@example.com instead of using the issue tracker.
As described here GitLab want to have a fast response. That means that it is useful to have a queue driver configured that run the jobs in the background. That means that if you use the sync driver it can happen that the response is to slow, so you get the webhook another time.
Test your webhook
On the GitLab pages with the webhook settings it is possible to test the webhook, use it to verify that everything works as suspected.
Cleanup your hooks
If you don't need the data saved in the webhook it can be a good idea to periodic remove the old data. Depending on the kind of hooks the body can be very big. This can be done on the end of your event listener or with a package like spatie/laravel-model-cleanup.
- GitLab for the great product, without that this package isn't needed.
The MIT License (MIT). Please see License File for more information.