Once the containers are online, execute the database initialization scripts to build schema structures and populate the environment with sample demo data.

: Once comfortable with dpsctl , you can automate tests using the included Hardware Emulation playbooks ( sim_rgs.sh , sim_grid.sh , sim_loadshed.sh ) for soak testing and CI/CD integration. The DPS SDK also supports custom Helm values, allowing you to import your own data center topology to simulate your infrastructure.

Move or copy this file into the ingestion directory specified in your .env file:

The repository contains a template configuration file that dictates network ports, data directories, and security tokens. Copy the template to create an active environment file. For Linux/macOS: cp .env.example .env Use code with caution. For Windows (PowerShell): powershell Copy-Item .env.example .env Use code with caution.

: To connect to your new environment, set the necessary environment variables:

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 &

With your environment variables defined, use Docker Compose to pull the pre-compiled images from the container registry and build local application configurations. docker-compose pull docker-compose up --build -d Use code with caution.

Open an updated web browser and navigate to the local hosting address: