Terminology

These terms appear throughout the documentation and the interface.

Panel — the central installation: database, web interface and REST API. It is the system of record and the thing operators log in to. Older documentation called this the master.

Node — a machine in your infrastructure that hosts game servers. A node runs the daemon.

Daemon — the agent process on each node. It receives requests from the panel and acts on the host: containers, processes, files, packages. A node without a running daemon cannot be controlled.

Wrapper — the supervisor that the daemon runs under. It downloads and integrity-checks daemon versions, starts and stops them, and exposes its own small control API so the daemon can be upgraded or restarted without the daemon itself being up.

Instance — one game or voice server. An instance belongs to a node and is driven by a module.

Module — an SDK plugin that teaches GameDash how to run a particular game. Modules declare which operating systems they support and expose resources such as setup and process handling. See SDK overview.

Resource — one capability inside a module, for example process handling or first-time setup. A module implements the resources it needs and inherits default behaviour for the rest.

Relay — the service that fans live events out to connected browsers over Socket.IO, so the interface can show console output and status changes as they happen.

FFI — the foreign function interface the SDK exposes to modules. It is how module code reaches into the platform to start a process, read a setting, or act on an instance. See The foreign function interface.

Infrastructure diagram