What or specific features are you looking to test during this demo? Share public link
Below, we’ll walk you through everything you need to know: what Project DPS actually is, how to get access to the playtest, and a detailed installation guide. By the end, you’ll be ready to jump into the game.
A terminal or command-line interface with administrative/sudo privileges. 2. Step-by-Step Installation Guide
sudo apt update && sudo apt upgrade -y sudo apt install -y curl gnupg lsb-release apt-transport-https ca-certificates
: Experiment with different combat styles using weapons like the Shotgun , Rifle , Laser weapon , or the Homing Missile Skill .
With the configuration file established, instruct Docker Compose to pull the necessary microservice images (frontend, core engine, database backend) and launch them in an isolated bridge network. Run the execution command in detached mode: docker compose up -d Use code with caution.
To achieve predictability, the team must embrace . A manual installation checklist—no matter how detailed—is a relic of fragile IT. For Project DPS, the demo install should be executed using infrastructure-as-code tools (such as Ansible, Terraform, or a simple Docker Compose script). The goal is a single command that, when run, provisions the entire stack: database schema, API endpoints, front-end assets, and sample data. Idempotency is the secret weapon: running the install script twice should produce the exact same state without errors. This guarantees that the team can reset the demo environment instantly between presentations, erasing any accidental data corruption or user interference. An automated install also demonstrates to stakeholders that Project DPS is not a bespoke artisanal product, but a robust system ready for handoff.
The demo relies on a configuration file to define root credentials, network ports, and encryption keys. The repository includes a template file that you must copy and adapt. Duplicate the template file: cp .env.example .env Use code with caution.
You should see a long list of pods, all with a status of Running .
The goal of this demo installation is to get a fully functional DPS environment running on your local machine. By the end of the process, you will be able to run kubectl get pods -n dps and see a series of containers in a "Running" state.
export DPSCTL_HOST=api.dps.sdk export DPSCTL_PORT=80 export DPSCTL_INSECURE_TLS_SKIP_VERIFY=true
Technical installations can sometimes hit snags. Here are solutions to common problems you might encounter.
ETCD_VER=v3.5.9 curl -L https://github.com/etcd-io/etcd/releases/download/$ETCD_VER/etcd-$ETCD_VER-linux-amd64.tar.gz -o etcd.tar.gz tar xzf etcd.tar.gz sudo mv etcd-$ETCD_VER-linux-amd64/etcd* /usr/local/bin/ rm -rf etcd* nohup /usr/local/bin/etcd --name demo-etcd --listen-client-urls http://0.0.0.0:2379 \ --advertise-client-urls http://127.0.0.1:2379 > /var/log/etcd.log 2>&1 &
