[+] Running 6/6 ✔ Container dps-database healthy ✔ Container dps-ingest started ✔ Container dps-engine started ✔ Container dps-ui started ✔ Container dps-demo-agent started ✔ Container dps-mock-traffic started
docker run -d --name dps-controller --restart unless-stopped \ -p 9000:9000 -p 9100:9100 \ -e ETCD_ENDPOINTS=http://host.docker.internal:2379 \ projectdps/controller:latest project dps demo install
A quick, step-by-step guide to install and run the Project DPS demo locally. [+] Running 6/6 ✔ Container dps-database healthy ✔
You can access the Project DPS demo through two primary platforms: : For a DPS, this might involve one power
Executing a successful Demo Install follows a disciplined methodology. First, the team defines the scope—limiting the demo to 20-30% of the full system’s complexity, yet including all high-risk integration points. For a DPS, this might involve one power distribution unit, one battery string, one monitoring client, and a simulated load. Second, the install is performed in an isolated test lab using installation scripts, configuration files, and network settings identical to those planned for production. Third, the team runs a predefined test suite: power failover, data replication latency, alarm generation, and user access controls. Crucially, the Demo Install is iterative. Bugs discovered—such as a misconfigured SNMP trap or a timeout in the authentication handshake—are logged, fixed, and retested within the demo environment before any code is promoted to the full build.
The Project DPS demo install offers several benefits, including:
Docker is the fastest way to get the demo running without worrying about local library conflicts. Open your or command prompt . Navigate to the extracted demo folder. Run the following command: docker-compose up -d