smee-client
smee.io
smee-client | smee.io | |
---|---|---|
4 | 1 | |
390 | 304 | |
2.1% | 1.3% | |
7.6 | 0.0 | |
8 days ago | about 1 month ago | |
TypeScript | JavaScript | |
ISC License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
smee-client
-
How We Converted a GitHub Tool Into a General Purpose Webhook Proxy to Supercharge Our Integration Development
Well, that will require a change in the smee-client as well. So maybe a follow-up?
-
Show HN: Send a GitHub webhook to a private URL
Neat stuff - certainly this problem crops up quite a lot where an internal server needs to get GitHub webhook data.
In the past, I've had good luck using a webhook proxy. I've mostly just used https://smee.io/ which is simple and lightweight although seems to be mostly abandonware at this point. I dockerized it so that it could be used in a Kubernetes cluster, which was very useful for my GitHub Actions build cluster: https://github.com/ethomson/smee-client
There's also Hookdeck, which I haven't used in production, but have played around with, and it seems conceptually the same, but can be made more Enterprisey. Whether that's a bug or a feature is probably up to you.
-
Deploy a GitHub Application to Cloudflare Workers
Using the same probot/smee-client shipped by Probot we divert the webhook URL to one on localhost for the development application, and for the production application we will enter a custom route.
smee.io
-
How We Converted a GitHub Tool Into a General Purpose Webhook Proxy to Supercharge Our Integration Development
My recommended starting point is to fork/clone the smee.io repo and get it working. And by working, I don't mean deploying it, but being able to build and run it locally to a point where you can place a break point in the code and have it pause there. This is necessary in order to customize any code. I actually had some issues doing that with the main branch as it was in commit 3a01759.
What are some alternatives?
ngrok - Expose your localhost to the web. Node wrapper for ngrok.
frp - A fast reverse proxy to help you expose a local server behind a NAT or firewall to the internet.
probot - 🤖 A framework for building GitHub Apps to automate and improve your workflow
GitGoat - GitGoat is an open source tool that was built to enable DevOps and Engineering teams to design and implement a sustainable misconfiguration prevention strategy. It can be used to test products with access to GitHub repositories without a risk to your production environment.
octokit.js - The all-batteries-included GitHub SDK for Browsers, Node.js, and Deno.
ziti-sdk-py - Ziti SDK for Python
cloudflare-worker-github-app-exampleassets
smee-client - 🔴 Receives payloads then sends them to your local server
cloudflare-worker-github-app-example - A Cloudflare Worker + GitHub App Example
node-config - Node.js Application Configuration
sish - HTTP(S)/WS(S)/TCP Tunnels to localhost using only SSH.