@scramjet/manager
v2.0.0
Published
Scramjet Manager
Readme
@scramjet/manager
The Manager is the orchestration layer that coordinates multiple STH Hubs, providing a single control plane for deploying, monitoring, and managing Sequences across your infrastructure. It collects health and status information from connected Hubs and exposes a unified API.
When to use
Use @scramjet/manager when you operate multiple STH instances and need centralized Sequence management, health monitoring, and API aggregation. Each Hub connects to a Manager; the Manager presents a unified view of all Sequences across all connected Hubs.
For cloud-platform deployments with spaces and multi-tenancy, see @scramjet/multi-manager.
Quick start
npm install @scramjet/managerThe standalone Manager package currently exposes a programmatic/package entrypoint rather than a fully featured public CLI. Run it from the workspace or from built distribution artifacts in deployments that include this package:
npm run start -w @scramjet/managerHubs connect to a Manager using legacy CPM registration fields plus the current verser2 host endpoint and TLS/mTLS configuration:
scramjet-transform-hub \
--cpm-id production-node-1 \
--cpm-url http://manager-host:8200 \
--verser2-host-url https://manager-host:2443Stability
This package is stable. The Manager API is part of the public runtime contract.
Configuration
The standalone Manager uses defaults from @scramjet/config and Manager types from @scramjet/types. File and CLI configuration loading is available through newer @scramjet/config command surfaces and the MultiManager package where implemented.
Manager-side verser2 TLS/mTLS settings are documented in the Manager and Hub connection guides. Do not assume Hub-side flags are also Manager-side flags.
See also
- Manager overview for architecture and deployment.
- Connecting Hubs for Hub-to-Manager topology.
- Transform Hub overview for the full platform picture.
Install
npm install @scramjet/managerImport
import { /* ... */ } from "@scramjet/manager";Documentation
See the package docs for full documentation.
