Installing the daemon

Installing the daemon is a single command on Linux. The script detects your distribution, fetches the matching package, and installs it.

Linux

Run as root:

curl -sSL https://raw.githubusercontent.com/SchokkerIT/GameDash-Daemon-Installer/main/install.sh | sudo bash

To install a specific release instead of the latest:

curl -sSL https://raw.githubusercontent.com/SchokkerIT/GameDash-Daemon-Installer/main/install.sh | sudo bash -s -- version=v1.0.0

The script requires curl, root privilege, and an x86_64, aarch64 or arm64 host. It reads /etc/os-release to pick between the .deb and .rpm build, so a distribution without that file is not supported.

What the package installs

  • The wrapper JAR
  • A gamedash system user
  • A systemd unit, gamedash-daemon
  • Configuration at /var/lib/gamedash/daemon.properties, with a symlink at /etc/gamedash/daemon.properties

The wrapper downloads the daemon itself on first run, so the package stays small and a daemon upgrade does not require reinstalling anything.

Configuration during install

The installer collects the details needed to reach your panel — the API domain and an authentication token — and writes them into daemon.properties. Every key it sets can be changed later; see Daemon configuration.

Service management

The package registers a systemd service, so the daemon starts at boot and restarts if it crashes:

systemctl status gamedash-daemon
systemctl restart gamedash-daemon
journalctl -u gamedash-daemon -f

No keystore step

Earlier versions required you to generate a Java keystore with keytool before the daemon would serve HTTPS. That is no longer necessary. By default the daemon generates an ephemeral self-signed certificate on every start, held in memory with a random password that is never written to disk.

Because that certificate is regenerated each boot and is not pinned, it gives you confidentiality but not server authentication. To pin, supply your own persistent keystore — see Daemon configuration.

Windows

Windows nodes are supported and installed differently. See Windows nodes.

Firewall

The panel must be able to reach the node. Allow the daemon and wrapper ports from the panel before expecting the node to come online — Ports & firewall lists them.

If you would rather not use the script

Manual installation covers running the wrapper directly, for hosts where the packaged route does not fit.