You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello. Do you have plans to implement JS back-end not only through CloudFlare? For me personally, and I think for many users of your library, it would be much more convenient to host these files on the same VDS.
The text was updated successfully, but these errors were encountered:
I'll take a look at how difficult it would be to make a Nodejs server (or something) with functional parity to the CloudFlare backend. I'll report back with my findings.
Do note, of course, that self-hosting means you won't benefit from CloudFlare's distributed systems, meaning clients will likely take a hit to latency when retrieving data.
However, I'm sure that if most of your players are regional (as they often are), this would be a very fair trade given the near-0 latency from the serverside 👍
Alright, after wrestling with it for a full day, I got something working!
I set up a new Docker Compose stack to run everything - is that a good solution for you?
Hello. Do you have plans to implement JS back-end not only through CloudFlare? For me personally, and I think for many users of your library, it would be much more convenient to host these files on the same VDS.
The text was updated successfully, but these errors were encountered: