Quartz sync: Jan 11, 2026, 4:26 PM
Some checks failed
Build and Push Quartz Wiki / build-and-push (push) Failing after 45s
Some checks failed
Build and Push Quartz Wiki / build-and-push (push) Failing after 45s
This commit is contained in:
@@ -0,0 +1,27 @@
|
||||
---
|
||||
title: Gitea Webhook and CI CD using Komodo
|
||||
publish: true
|
||||
tags:
|
||||
-
|
||||
---
|
||||
|
||||
# Gitea Webhook and CI CD using Komodo
|
||||
|
||||
You need to whitelist the url you're sending a webhook to in the `config/app.ini` file.
|
||||
|
||||
The `[webhook]` section might look something like that
|
||||
|
||||
```ini
|
||||
[webhook]
|
||||
|
||||
ALLOWED_HOST_LIST = loopback,private,*.vorpax.dev
|
||||
```
|
||||
|
||||
|
||||
To my own dismay Gitea doesn't offer granular configuration for webhook dispatch (for instance, to trigger your webhook only when some actions are completed).
|
||||
|
||||
Neither does Komodo enables you to easily verify some basic parameters inside of the webhook's json body.
|
||||
|
||||
In the future, I'll probably setup all of that in CI/CD runners like Gitea Actions, though I would likely trade convenience for a much larger potential to extend CI/CD usage in my Homelab.
|
||||
|
||||
I'm actually contemplating an eventual deployment of GitLab on Gerboise, I don't really know if it is worth the ressource overhead...
|
||||
Reference in New Issue
Block a user