hosting/mash-playbook
1
0
Fork 0
Code Pull requests Activity

Merge pull request #153 from sergiodj/forgejo-woodpecker-integration-doc

Browse source 
Better explain how to integrate Forgejo and Woodpecker CI
This commit is contained in:
Slavi Pantaleev 2024-02-25 17:09:15 +02:00 committed by GitHub
commit 806eda3fd7
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
docs/services/forgejo.md
View file

@ -57,3 +57,19 @@ Going there, you'll be taken to the initial setup wizard, which will let you ass
## Recommended other services
You may also wish to look into [Woodpecker CI](woodpecker-ci.md), which can integrate nicely with Forgejo.
## Integration with Woodpecker CI
If you want to integrate Forgejo with [Woodpecker CI](woodpecker-ci.md), and if you plan to serve Woodpecker CI under a subpath on the same host as Forgejo (e.g., Forgejo lives at `https://mash.example.com` and Woodpecker CI lives at `https://mash.example.com/ci`), then you need to configure Forgejo to use the host's external IP when invoking webhooks from Woodpecker CI. You can do it by setting the following variables:
```yaml
forgejo_container_add_host_domain_name: "{{ devture_woodpecker_ci_server_hostname }}"
forgejo_container_add_host_domain_ip_address: "{{ ansible_host }}"
# If ansible_host points to an internal IP address, you may need to allow Forgego to make requests to it.
# By default, requests are only allowed to external IP addresses for security reasons.
# See: https://forgejo.org/docs/latest/admin/config-cheat-sheet/#webhook-webhook
forgejo_container_additional_environment_variables: |
FORGEJO__webhook__ALLOWED_HOST_LIST=external,{{ ansible_host }}
```