0974de1df5
CLAUDE.md points at .claude/skills/scadabridge-components/SKILL.md as the component catalog and .claude/skills/scadabridge-cluster-ops/SKILL.md as the source for the management URL, credentials and rebuild/redeploy commands — but neither file was tracked, so a fresh clone got instructions referencing content that was not there. Only the skill files are added; .claude/settings.local.json and scheduled_tasks.lock stay ignored via .gitignore as before.
1.6 KiB
1.6 KiB
name, description
| name | description |
|---|---|
| scadabridge-cluster-ops | How to drive the local ScadaBridge docker cluster — CLI management URL and credentials, config file, rebuild/redeploy commands, and the infra services. Use when running CLI commands against the cluster, rebuilding after server-side changes, or starting the local test infrastructure. |
ScadaBridge Cluster Ops (Docker / OrbStack)
- Management URL:
http://localhost:9000— the CLI connects via the Traefik load balancer, which routes to the active central node. Direct access: central-a on port 9001, central-b on port 9002. - Test user:
--username multi-role --password password— has Admin, Design, and Deployment roles. Theadminuser only has the Admin role and cannot create templates, data connections, or deploy. - Config file:
~/.scadabridge/config.json— storesmanagementUrland default format. Seedocker/README.mdfor a ready-to-use test config. - Rebuild cluster:
bash docker/deploy.sh— builds thescadabridge:latestimage and recreates all containers. Run this after code changes to ManagementActor, Host, or any server-side component. - Infrastructure services:
cd infra && docker compose up -d— starts MS SQL, OPC UA, SMTP, and REST API. These are separate from the cluster containers indocker/. LDAP is NOT started here — it is the shared GLAuth on10.100.0.35:3893(dc=zb,dc=local); source of truth and config:scadaproj/infra/glauth/. - All test LDAP passwords:
password(seescadaproj/infra/glauth/config.tomlfor users and groups; canonical cross-app login:multi-role).