joshheng / jackboxproxy Goto Github PK

While it's cool, it's not required, you just have to understand a bit more about how they had the API hosted.

It's hosted using AWS Load Balancers, which use CNAME records on the DNS side, so you can just grab the CNAME and set the host in the fetch request.

Here is a standalone cloudflare worker attached in this gist is two javascript files.

jackbox-proxy-with-ecast.js - Proxies both the ecast api and the frontend
jackbox-proxy.js - Proxies only the frontend (has the exact same effect to the user)

However, during more testing there is absolutely no need to proxy the ecast api (it's on a different host already) as the only point of this proxy should be to have users go to a different domain, and stay on that domain during the game, of course on some sites their API is cors protected, meaning you would have to proxy it, this one however is not and you only need to proxy the frontend for everything else to work.

Sharing this simply to show how I've done it without the unnecessary vercel function. (no matter how much I love vercel haha)