kemitix/git-next
1
1
Fork 1
Code Issues 14 Pull requests 1 Projects 1 Releases 41 Packages Wiki Activity Actions

docs: add missing notification config details
All checks were successful
Rust / build (push) Successful in 2m3s
Details
ci/woodpecker/push/cron-docker-builder Pipeline was successful
Details
ci/woodpecker/push/tag-created Pipeline was successful
Details
ci/woodpecker/push/push-next Pipeline was successful
Details

Browse source
This commit is contained in:
Paul Campbell 2024-07-28 18:29:20 +01:00
parent a56c6df3f1
commit 991d0d1a08
1 changed files with 10 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
crates/cli/README.md
View file

@ -100,6 +100,16 @@ This is the address and port that your reverse proxy should route traffic to.
- **addr** - the IP address the server should bind to - **addr** - the IP address the server should bind to
- **port** - the IP port the server should bind to - **port** - the IP port the server should bind to
#### notification
The server should be able to notify the user when manual intervention is required.
Currently this is only available via sending a Webhook message.
- **type** - one of `None` or `Webhook`
- **webhook** - the URL to POST the notification to
See [Notifications](#notifications) for more details.
#### webhook #### webhook
Your forges need to know where they should route webhooks to. This should be Your forges need to know where they should route webhooks to. This should be