Contents

• Contents
• What is funkypenguin/concourse-webhook-bouncer ?
• Why should I use this?
• How do I use this?
• CHANGELOG

---

This container is maintained by Funky Penguin's Geek Cookbook, a collection of "recipes" to run popular applications on Docker Swarm or Kubernetes, in a cheeky, geek format.

Got more details at:

• Forums
• Friendly Discord Chat
• Funky Penguin's Geek Cookbook
• Patreon
• Blog

---

What is funkypenguin/concourse-webhook-bouncer ?

My favorite open-source, self-hosted CI system, Concourse, includes primitive support, allowing webhooks to trigger jobs. The downside is that the Concourse UI has to be exposed to the Internet for the webhook URL to be reachable.

This container is a simply nginx proxy which will pass on valid Concourse webhook calls to an internal (non-publicaly-exposed) Concoruse URL, and disregard any other riffraff.

I.e., a bouncer.

Why should I use this?

You should use it if you:

1. Run Concourse-CI on a non-publicaly accessible URL
2. Want to respond to webhooks

How do I use this?

Run the container with the following environment variables:

• CONCOURSE_URL : Set this to the full URL to your Concourse instance, i.e. https://concourse.batcave.org
• RESOLVER : Set this to choose an optional resolver. A default of 1.1.1.1 will be set.

CHANGELOG

• Initial release : (30 Aug 2019)