sish VS smee-client

sish uses ssh tunneling that you can read about in their docs: https://ssi.sh/

Tunneling services can be considered as a solution in some cases. Services like ngrok, frp, localtunnel and sish create a public endpoint that tunnels communication to your local endpoint via a tunnel client.

My favourite one is https://github.com/antoniomika/sish

It uses SSH as the method of opening the remote tunnel to the public server.

Why not forget about Cloudflare and a VPN but get a 3 euro Hetzner server and install https://github.com/antoniomika/sish for dynamic DNS through SSH + Traefik with a DNS resolver and have yourself a wildcard certificate. This way you can host any service from home as long as you run a port forwarding service through SSH with a one liner on Ubuntu. Better yet make an alpine docker image with a command to route traffic to your local service for even more isolation. 😘

Personally I’ve been using sish[1] recently, lots of ngrok alternatives out there now, especially as the pricing went a bit weird

[1] https://github.com/antoniomika/sish

i used to use a similar tool called inlets but they removed the open licensing. i now self host a sish server (https://github.com/antoniomika/sish) which also uses ssh for the reverse tunnel client. so much simpler!

- Sish : Because I don't want to pay for ngrok anymore (https://github.com/antoniomika/sish)

They could create a tunneled connection. Take a look at ngrok.io or ssi.sh

Well, that will require a change in the smee-client as well. So maybe a follow-up?

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.

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.