1. Launch Diarkis Server Locally
Introduction
This page explains the steps for launching the Diarkis server in your local environment using Diarkis Server Template. We recommend going through these steps before starting development with Diarkis.
Environment Setup
To introduce the server template, Go version 1.22 or later is required.
The installation method varies by platform, so please follow the official documentation for installation. https://go.dev/doc/install
Diarkis server development can be done on macOS, Linux, and Windows.
In Windows environments, operation is confirmed with WSL1 on Windows 10 (Ubuntu 20.04). Since WSL2 does not support UDP port forwarding, please use WSL1.
If you are not using WSL1, you can convert your WSL environment by starting PowerShell with administrative privileges and executing the command wsl --set-version Ubuntu-20.04 1
.
Generating a Project from the Server Template
First, clone the repository by executing
git clone https://github.com/Diarkis/diarkis-server-template.git
in any PATH.Execute the following command to generate the project. The output will be an absolute path specified as
output
.
The project ID
and builder token
specified here are credentials issued to developers with a Diarkis enterprise license. Since the core of Diarkis is built as a closed source and implemented in Go, it is necessary to use diarkis-cli to build.
If you need an older version, you can either check out a tag of the desired version or download it from the release list.
Setup
Execute the following command in the generated project.
This will download various resources needed for development (e.g., references for using code completion).
Generating Server Binaries
To generate binaries for local use, execute the following make task.
After executing the above, Diarkis binaries will be generated under remote_bin
.
Starting the Server
Start the MARS, HTTP, and UDP servers.
Retrieving Connection Information
If mars, http, and udp are running, you can retrieve connection information using curl as follows. This completes the server setup.
The above HTTP endpoint signifies that uid test
has been authenticated against the UDP server. The information returned from here can be used by various client libraries to exchange packets.
Last updated