GitLab webhooks handler
This is simple server (receiver) for GitLab’s webhooks feature.
Alternatives
Installation
Make sure you have Python 2.6+/3.2+ properly installed (Windows/Linux). Then just type [sudo] pip install glhooks in your favorite shell. Now you have glhooks installed so you can run it like this python -m glhooks <path_to_config_file>.... You can find skeleton for the configuration file in git repository in config/config.ini.
I recommend Supervisor or similar application to run the glhooks server. Install it via [sudo] apt-get install supervisor. You can find the example of Supervisor configuration file for glhooks in git repository in config/glhooks.conf. But you can just create some shell script and copy it into /etc/init.d/ (example in git repository in config/glhooks.sh).
Next step is to generate a SSH key without the passphrase: ssh-keygen -b 4096 -t rsa. Then add the generated SSH public key to your GitLab account. If you have multiple SSH keys in $HOME/.ssh/ you probably has to create file $HOME/.ssh/config. You can find the example file in git repository in config/config.ssh.
Finally add the hook http://server.example.com:8000/ into your project webhooks at GitLab.
Updating
When you change at least one of the configuration files you has to restart glhooks server by [sudo] supervisorctl restart glhooks or [sudo] service glhooks restart.
Contributing
Feel free to send a pull request or to report an issue.
Changelog
0.1.0 (2014-01-14)
First public release.
Metadata
Release files for glhooks 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| glhooks-0.1.0.zip | 17.9 kB | Without provenance | Details for glhooks-0.1.0.zip |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| glhooks-0.1.0.win32.exe | Details for glhooks-0.1.0.win32.exe | |||
| glhooks-0.1.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for glhooks-0.1.0-py2.py3-none-any.whl |
Total release size: 238.0 kB
Release files / glhooks-0.1.0.zip
| Download URL | glhooks-0.1.0.zip |
|---|---|
| Size | 17.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0131c7b6da8f055fc7a9bdaf17bb7cba8c70bb940809ae2e9a5dd4eeeff6a985
|
|
BLAKE2b-256 checksum How to use checksums |
ecb0b428f8ed575c6c940800725db98ab1969445a80eeffbbb470ece69f18056
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / glhooks-0.1.0.win32.exe
| Download URL | glhooks-0.1.0.win32.exe |
|---|---|
| Size | 205.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
edace17c2b0c658a21579455dea193d3aa7244cf078a5ec6af92584e4c85e0f7
|
|
BLAKE2b-256 checksum How to use checksums |
8001e6714bf64649882eb222e1f449de75179c7b113d81f0b22a2cad83114aa4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / glhooks-0.1.0-py2.py3-none-any.whl
| Download URL | glhooks-0.1.0-py2.py3-none-any.whl |
|---|---|
| Size | 14.2 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
241356c4753071b8e544db7233373d333d85189d34811e5e30230daad3aa05a5
|
|
BLAKE2b-256 checksum How to use checksums |
3f81c8897d72cba617a240bfe67ce6e426ff69b884cb70bcf75e2e4a906d72ee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for glhooks 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.