run-all-workers-site.md

title	Run the supported Worker fleet with mock devices
description	Boot multiple backend Workers as supervised PM2 or Docker processes, each connected to mock hardware, for a complete end-to-end site
docs@tether_slug	guides/deployment/run-all-workers-site
notes	in mdk detailed operational changes are kept in package docs to prevent drift from the runnable source

This page directs you to the correct location for the prerequisites, run command, smoke test, and troubleshooting.

Overview

Use this example when you want the to run a demo for multiple configured Workers across the device families - for miners, containers, power meters, sensors, and pools - running as separate processes. Each talks to mock hardware that speaks the real wire protocol. The site Gateway plugin surfaces all device data through a single /site HTTP API.

This example runs a microservices topology. Use this when:

• You want to explore the supported Worker fleet and its telemetry in one running system
• You are testing PM2 or Docker orchestration before deploying to hardware
• You want real driver code running its full connect, collect, and command paths (only the endpoints are localhost mocks instead of hardware)
• You want the site Gateway plugin as a starting point for your own /site API

Note

You have a choice of deployment topologies from microservices to single-process.

Run the example

Follow the site example:

• Start with the prerequisites
• Choose your launch method:
  • Use PM2 for local process supervision on one host
  • Use Docker when you want containerized services or Compose-managed startup
• Verify the fleet is up with a single curl

Next steps

• Understand the trade-offs between deployment topologies
• Run a single-process site for the simpler local topology
• Extend the Gateway HTTP API with custom plugins
• Browse the functions that wire together the Kernel, device Workers, and the Gateway HTTP
• Build your own Worker from scratch

Links