quickstart guide. You can get one of these up and running in Digital Ocean in about 5 minutes
meseta.dev/serverkit-ga...

Today, I have another task for the GML HTTP server. So I'm updating it - adding type annotations that are part of Feather, support for deflate content-encoding, and a few other goodies as well I have some even dumber things planned for this

As well as allowing the sharding service (responsible for managing the fleet of gamemaker servers) to control which room the server is running, or to send the server Idle when it's not being used

Since HTTP and REST in particular are the kings of server-side stacks (or perhaps at least the common denominator), it made sense to give GameMaker the ability to be an HTTP server

For example, in our MMO backend, we use this to provide kubernetes /healthz healthchecks.

Why did I do this? A couple years ago when I was experimenting with running GameMaker on the server, in particular inside kubernetes, I realized that one of the key things that prevent it from being used as part of server stacks is not having a nice way to interface with it

glad to be here. Who should I follow here?