Split Oore across Macs
Use Control plane, Runner, Web node, and CLI only profiles across separate Macs.
Use split roles when one Mac cannot provide every required service.
The guided v0.1.42 lifecycle supports macOS only. Published Linux web archives are standalone assets, not a guided Web node installation.
Supported compositions
| Need | Supported profiles |
|---|---|
| Separate build host | Control plane and one or more Runners |
| Separate browser ingress and build | Control plane, Web node, and one or more Runners |
| Remote operator CLI | CLI only with a ready Complete or Control plane |
| Extra build capacity | Complete with one or more remote Runners |
What you need
- A supported Mac for each guided profile.
- A protected network path between each remote profile and the control plane.
- HTTPS for a remote control-plane URL, unless a separate private network protects HTTP.
- An Owner or Admin Oore API token for each Runner.
- Protected browser ingress for a browser-facing Web node.
- A single-use pairing code for a Trusted Proxy Web node.
1. Prepare the control plane
On the control-plane Mac, install the CLI and select the Control plane profile:
curl -fsSL https://oore.build/install | bash
~/.oore/bin/oore install --profile control-planeComplete terminal setup before you add another profile. The control plane must report that setup is ready.
Use Identity provider or Trusted proxy access for a non-loopback browser route. Local Only access remains loopback-only.
2. Connect a browser client
Use a Web node only when the product web proxy must run on another Mac.
The control plane must use Identity provider or Trusted Proxy access. A Web node cannot sign in to a Local Only control plane.
For Trusted Proxy access, create a pairing code on the control-plane Mac:
oore frontend inviteThen install the Web node profile on the browser-ingress Mac:
curl -fsSL https://oore.build/install | bash
~/.oore/bin/oore install --profile web-nodeSupply the ready control-plane URL. For Trusted Proxy access, also supply the new pairing code.
Keep the Oore web listener on loopback. Terminate TLS at the protected ingress on the same Mac.
The pairing code is single-use and expires. Create a new code after an expired or consumed attempt.
You can instead connect the hosted UI or a self-hosted static UI.
The Control plane profile has no local web service. Connect one browser client before you create tokens for other Macs.
3. Add a Runner
On each build Mac, install the Runner profile:
curl -fsSL https://oore.build/install | bash
~/.oore/bin/oore install --profile runnerUse the connected browser client to sign in to Oore. Open Settings > API tokens and create an Owner or Admin token.
Copy the token when Oore shows it. Supply that token and the ready control-plane URL during Runner setup.
Oore registers the Runner and starts its macOS service.
Install Git and each required platform tool on the Runner Mac. Missing build tools do not block Runner setup.
4. Add a CLI only operator
Install the CLI only profile on another operator Mac:
curl -fsSL https://oore.build/install | bash
~/.oore/bin/oore install --profile cli-onlySupply the ready control-plane URL. For a non-loopback control plane, use the connected browser client to create a token under Settings > API tokens.
Supply that token during setup.
Verify the composition
On each Mac, run:
oore status --daemon-url https://oore.example.comOpen the protected browser URL. Make sure that Settings > Runners shows each expected Runner as online.
Run a small build from an approved repository. Make sure that a remote Runner claims the build.
Troubleshooting
If remote setup fails, make sure that the control plane is ready and reachable through the protected path.
If Web node pairing fails, create a new pairing code. Then repeat oore setup on the Web node.
If Runner registration fails, create a current Owner or Admin token under Settings > API tokens.
Next step
Configure External Access for the browser entry point. Then monitor every role.