Operate Oore

Task guides for browser clients, runners, storage, deployment, maintenance, and troubleshooting.

These guides keep an Oore instance running and grow it when your team needs more. Start from the one-Mac Complete install. Add one piece at a time, and check it works before you add the next. To decide what to add, read Which setup do I need?.

Reach Oore from other devices

Connect the hosted UI at ci.oore.build.
Connect Cloudflare Tunnel and Access to put a loopback backend behind HTTPS.
Self-host the static UI.
Add another Oore instance to the same browser, and switch between instances.

Build on more Macs

Add a Direct macOS runner on another Mac.
Route builds with runner labels.
Run builds in VMs for a clean machine per build.
Manage dependency caches.
Split Oore across Macs, or run a Web node on Linux.

Store artifacts

Configure artifact storage on the Mac or in S3 or R2.

Maintain

Monitor Oore.
Create and verify a backup before every upgrade.
Upgrade Oore on the current channel, or choose a release channel.
Restore a backup when you need to.

Fix problems

Troubleshoot Oore routes each symptom to the right check.
Reset an Oore installation only after narrower fixes fail.
Report an issue with the details maintainers need.
Known limitations lists what Oore does not support.

Next step

Monitor Oore, then create and verify a backup.