git-twitch VS ngrok

Are you planning on using our Twitch chatbot? Which server is your go to choice? Let us know your favourites, and remember, you can clone, fork, or contribute to Git Twitch. We can't wait to see more Twitch streams making use of notifications for GitHub-specific events.

Since we had already been doing some work on this chatbot, we already had the repo from Bdougie. The first thing we need to check, is that we're up to date with any changes Bdougie has done. We noticed immediately that Bdougie's repo was ahead of the version I had. So we need to make sure we have the latest version, without compromising the changes I already made.

Making a Twitch bot and using the GitHub API is no trivial task. Luckily, Bdougie has been doing some work on it already. He put together an open source repo which utilises webhooks to talk to Twitch. By forking this repo and following the instructions, you can make the Twitch bot work for your channel.

Many good reverse proxy solutions currently exist on the market such as ngrok and Cloudflare tunnels. They give one the ability to reliably run a tunnel and ensure it does not go down. They also offer the ability to securely access their links using whitelisted IP addresses or by using HTTP Basic Authentication.

These is a very common problem. Luckily, it's been solved already. My go-to tool for this was ngrok or localtunnel. Both of these tools are great, but they didn't fit my needs perfectly.

Ensure your app works as expected and provides a good user experience by thoroughly testing and debugging. Utilize tools like Chrome DevTools or Firefox Developer Tools to inspect and modify your app’s code, network, and storage. Employ tools like ngrok or localtunnel to expose your local development server to the internet, enabling testing on various devices and browsers.

ngrok

Tunnels (CloudFlare vs. Ngrok)

We need to make our WhatsApp API accessible on the internet so the trigger.dev cloud service can connect to it. We can do that by running ngrok in a separate terminal.

This means that Cronitor must have an endpoint that it can reach. Normally, we can't do that when developing on a personal machine. For this tutorial, however, we can use ngrok to establish a tunnel to our local Django application for testing purposes.

There are so many weird suggestions in the comments. I'm surprised nobody has mentioned ngrok https://ngrok.com/ (there are many competing alternatives as well). It makes exposing local service over HTTPS trivial. It's been used heavily in most of my engineering orgs.

Ngrok: This provides about 2hours on the free account but requires account registration and adding your authtoken, and starting it is as simple as running ngrok http 8080