Reset an Oore installation

Use a reset only when setup or state recovery cannot repair the installation.

A reset removes owned components and canonical Oore data. For a control plane, this includes users, projects, builds, configuration, and encrypted credentials.

Artifact payloads need a separate retention or removal plan.

What you need

• Console access to the control-plane Mac.
• A verified backup.
• The default managed data layout.
• The current device profile and intended release channel.
• The first owner identity for the replacement instance.

1. Record the current installation

Record the current profile, release channel, install root, and release repository.

The default install root is ~/.oore. The installation manifest is ~/.oore/install-manifest.json.

Keep the verified backup outside the installation root and the canonical Oore data directory.

2. Review the purge plan

Run:

oore uninstall --purge

Read the displayed plan before you approve it. Oore checks manifest ownership before it stops services or removes files.

Without an interactive terminal, activate administrator access first. Then add --yes:

sudo -v
oore uninstall --purge --yes

Purge refuses unsafe paths, foreign services, and unverified bootstrap-only installations.

3. Reinstall the CLI and profile

For the default stable channel, run:

curl -fsSL https://oore.build/install | bash
~/.oore/bin/oore install --profile complete

Replace complete with the profile that this Mac needs.

For a custom channel or install root, pass the recorded bootstrap values. Then use the CLI from that install root.

Interactive installation continues to setup. For headless installation, run oore setup with explicit values or a private configuration file.

Verify the result

Setup must end with <Profile> setup is ready.

For Complete, Control plane, or CLI only, run:

oore status

For a remote Runner or Web node, run:

oore status --daemon-url https://oore.example.com

For Complete or Control plane, make sure that the new owner can sign in.

If the deployment uses a Runner, make sure that each expected Runner is online.

For a Runner or Complete profile, run a small build from an approved repository.

Keep the backup until the replacement instance passes all acceptance checks.

Troubleshooting

If purge reports a foreign service or unsafe path, stop. Preserve the output and report the problem.

If setup stops, correct the reported input. Then run oore setup again to resume the recorded profile.

Next step

Monitor Oore.