Supported platforms

This page lists the machines a dynamo-core instance, the SDK and dynamo-guard are tested on, and how each one is tested.

What you need

Platforms

PlatformHow it is tested
Linux x64 (Ubuntu 24.04)The full gate runs on pushes to main and to the work branches; a push that changes only internal Markdown files does not start it, and a newer push cancels an older run on the same branch
macOS arm64 (Apple silicon)The platform smoke workflow, started by hand
Windows x64The platform smoke workflow, started by hand
Any other machinemake platform-smoke, the same steps, run locally

The container image is built on Debian bookworm with Node.js 22, for linux/amd64 and linux/arm64.

The platform smoke covers what a developer does first on a new machine:

  1. Build the SDK, the core host and the hosted entry's packages.
  2. Run the Control Mode SDK quickstart.
  3. Bring dynamo-guard up from its README quickstart, against an offline mock upstream.
  4. Boot a core and open, read back and close one budget with the SDK.

It runs on loopback only, with no key and no account. It does not run the property suites, the chain tests or the gateway containers. On macOS arm64 and Windows, only the platform smoke steps are tested.

Run the smoke on your machine

cd "$DYNAMO_REPO"
pwd
pnpm install --frozen-lockfile
make platform-smoke

Every step runs even when an earlier one fails. The run ends with a table that gives each step's result and time, and the line platform-smoke: PASS on <platform> <arch> or platform-smoke: FAIL (<steps>) on <platform> <arch>; the exit code is non-zero when any step failed. To run some of the steps only, set PLATFORM_SMOKE_STEPS to a comma-separated subset of build, control, guard and budget, for example PLATFORM_SMOKE_STEPS=build,budget.