@twinark/devops-cli

CLI toolkit for the Digital Twin platform DevOps. Manages the full lifecycle: configure → activate → build → run → publish.

Install

npm install -g @twinark/devops-cli

Usage

devtools <command> [options]
devtools --help

Run devtools from the project root (the directory that contains Digital-Twin-Capabilities/, Digital-Twin-Apps/, etc.). Use --root <path> to override.

Interactive vs non-interactive

By default, commands prompt for any missing options.

For scripted / CI use, pass --yes (alias --non-interactive) and provide every required value via flags — otherwise the command will block on a TTY read and hang in non-TTY shells.

# Interactive — prompts for project, hostname, overrides, etc.
devtools configure

# Non-interactive — all values supplied, no prompts
devtools --yes configure \
  --codename Project \
  --hostname host.docker.internal --port 8050 \
  --no-external-dev-server

Discovery commands (list-projects, list-overrides, list-modules, list-registry-modules) are always non-interactive — use them to fetch valid values before scripting other commands.

create-pbc is always interactive.

Common commands

| Command | Purpose | |---|---| | configure | Set up environment and generate deploy script | | activate-project-models | Select active modules | | build / build-module <m> | Build all / one module | | run | Start the application (docker compose up -d) | | publish / publish-module <m> | Push images and create release | | dependencies | Dependency and security audit | | load-tests | Run OpenAPI load tests | | clean | Remove build artifacts |

Requirements

• Node.js 18+
• Docker + Docker Compose