Skip to main content
Version: 5.x

Edgegap

Redwood provides a first-class integration with Edgegap by using the edgegap provider. This integration focuses on the Deployment API.

Preparing the Game Server​

Edgegap requires you to connect a Container Registry where the Docker image for the game server is located. You can either use Edgegap's built-in Container Registry or host it elsewhere. You need a Container Registry for Redwood services as well.

You'll follow the steps for Building and Pushing Docker Images to publish the game server image to the Container Registry.

Configuration​

To use Edgegap, you'll need to add config overrides for the Realm Instance Config game-servers.edgegap.* variables.

game-servers:
  edgegap:
    credentials:
      # Your Edgegap API token - get this from your Edgegap dashboard
      # This can be a secret in the secrets provider
      api-token: ""

    # The application name in your Edgegap account
    # This must match the name of your application in the Edgegap dashboard
    application: ""

    # The version of the application to deploy
    # This must be the match the version slug used in the Edgegap dashboard
    version: ""

A few other things to know about the Edgegap provider:

  • Regions come from Edgegap's location beacons, so a single realm can place servers anywhere Edgegap has a location. Clients ping the beacons and matchmaking uses those results.
  • Cross-server Sync Items are disabled with Edgegap, since the servers aren't in your cluster to share Redis. Persistent Items, World Data, and player data still work.
  • The Realm Backend must be reachable from the internet. Edgegap servers' sidecars connect to the realm's backend.connection.external host, which must be a public hostname (not an IP address). The kubernetes config environment sets it to an internal cluster hostname for Agones, so override it for realms that use Edgegap.
  • Extra command-line arguments for the server come from game-servers.agones.arguments (it's shared by every provider that runs packaged servers).
  • You can use Edgegap for only some profiles or zones by overriding the provider in your game profile.

Using Edgegap Game Servers in Development​

warning

Similar to deploying to Kubernetes, you need to be able to package dedicated servers before you can use Edgegap.

In development it's easier to use the local and agones providers with the Dev Initiator and Kubernetes respectively, but it's may be more cost effective for you to use the edgegap provider in cloud/production environments until player demand reaches a point where agones and self hosting your game server nodes becomes more cost effective, especially for match based games.

However, you can use the edgegap provider with the Dev Initiator for testing viability and integration.

Install ngrok​

ngrok is a free service that gives you a public endpoint that forwards to a port on your local machine. We'll be using it so the game servers on Edgegap will be able to talk to the backend services in the Dev Initiator.

  1. Signup for a free account at https://dashboard.ngrok.com/signup

  2. Login and follow the Connect instructions on https://dashboard.ngrok.com/get-started/setup.

    note

    You can choose which ever Installation method you want in the instructions as long as the ngrok executable is on your PATH.

    note

    For now you don't need to follow the Secure your endpoint steps, but you can if you want for extra security. This guide will assume you didn't.

  3. Open a terminal and run ngrok http 3010. This will open a tunnel that the Realm Backend service will use.

  4. You should see something like the below, noting the Forwarding line:

    ngrok                                                                                                   (Ctrl+C to quit)
    Policy Management Examples http://ngrok.com/apigwexamples
    Session Status                online
    Account                       Your Name (Plan: Free)
    Update                        update available (version 3.14.0, Ctrl-U to update)
    Version                       3.3.2
    Latency                       -
    Web Interface                 http://127.0.0.1:4040
    Forwarding                    https://***.ngrok-free.app -> http://localhost:3010

    Connections                   ttl     opn     rt1     rt5     p50     p90
                                  0       0       0.00    0.00    0.00    0.00

Configuration​

In your Realm Instance Config for your custom config environment (e.g. realm/instances/default.yaml), switch the provider to edgegap and specify the ngrok host so the Edgegap servers can connect to your local Dev Initiator:

game-servers:
  provider: "edgegap"

backend:
  connection:
    external:
      host: "***.ngrok-free.app" # Copy the public **Forwarding** address from the `ngrok` terminal without the `https://`
      port: 443 # Keep this at 443, not 3010
      tls: true

Test​

Run the backend like you did in the getting started section.

You can now start a match from your main menu like you did in the getting started section.

warning

In some scenarios you can test with the Edgegap servers while running PIE, but you may have issues actually connecting the client to the server. You'll be in the loading screen about to connect to the server but then get kicked back to the main menu. Check the Output Log to see if you received a warning/error (search for checksum mismatch):

LogNetPackageMap: Warning: GetObjectFromNetGUID: Network checksum mismatch.

In these cases, you'll need to package a Windows client (the same version as the server you uploaded to Edgegap) instead of using PIE.

tip

A packaged client uses the Director Uri saved in your project's config files. If your packaged client can't connect to your local Dev Initiator, check that Project Settings > Plugins > Redwood > Director Uri is set to your Dev Initiator (e.g. ws://director.localhost:3001) in Config/DefaultProjectSettings.ini.

You can also add a redwood.json file next to the packaged game (e.g. WindowsClient/YourProjectName/redwood.json) with the below contents, and restart the client. The redwood.json file comes in handy if you need to point a pre-packaged client to a different Redwood Backend instance (e.g. running Redwood at an internet-less conference but using the latest production client). It can be disabled or required to be signed in the Redwood settings.

{
  "directorUri": "ws://director.localhost:3001"
}