neko VS ngrok

I personally use neko-rooms with my friends for this purpose. Just let's all share a browser in a browser with plenty of options (Firefox, Chromium, Brave, etc.). You can also just use standard neko if you don't need multiple rooms.

Hey, you do you. It just sounds like an expensive way to avoid owning the hardware you want to debug to me.

Also, not to burst your bubble, but there are a few projects out there that do more-or-less what you're describing:

- https://store.steampowered.com/remoteplay/#together

- https://github.com/m1k1o/neko

If you're having fun, then continue by all means. I've just been nerd sniped by your cloud costs and I'm having flashbacks to seeing six-figure monthly AWS bills at startups that refused to buy their own GPU compute.

You could spin up something like Kasm Workspaces, Neko or Docker Webtop.

I ran into neko https://github.com/m1k1o/neko recently which has similar. It's more application centric than desktop centric, but both offer multi-player experiences & I just think that is the absolute coolest.

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