API guide for game hosting
Last updated
Last updated
Looking for a quick start on game deployment within the Game Hosting platform using our Game Server Orchestrator? Here's how it works:
Once that's registered, upload your build to the origin.
¹ the largest factor in deployment time is the size of your build archive that needs to be downloaded ² in order to deploy game servers you first need to have at least one bare metal or flex metal server active in your account
Before you can begin, you need to ; a secure web server that hosts your build archives. A build origin can be a web server that you host yourself, or you can use a build origin provided by us.
Our platform needs to have some information about the application you're going to deploy. As such, you have to telling us what kind of application it is (a game application to begin with) and you must give it some , like a network (game) port that clients can connect to.
Next you must point to your build archive from within an . Here you enter things like the name of the executable, along with any startup parameters that we need to pass to the game server when starting it.
From within a you point to an Application Build you want to deploy. You need this step because you must point to this later on in the process.
A is the top most element in your deployment hierarchy. It encapsulates all Fleets that must be grouped together for a single purpose. E.g. you can have a development, testing and production environment.
Now it's time to tell the platform where you want your game servers deployed by creating a . Here you must define your geographical deployment regions (based on where you rent bare metal servers from us) and optionally add cloud bursting locations to each region.
A ties all previously created elements together, defining for the platform all details it requires in order to deploy your game servers.
Finally, you must . Sit back and see your game servers come online within a few minutes(1)(2)
