How Oore works
Short explanations of the choices and boundaries behind Oore, linked from the tasks that need them.
These pages explain why Oore behaves the way it does. Read one when a task raises a question. You do not need them before your first build.
Before you install
- Which setup do I need? compares Local Only and External Access, local and connected repositories, browser clients, and one Mac against several.
- How Oore is structured shows what the browser
client,
oore,oored, and the Direct macOS runner each do.
While you build
- How a build moves from queue to artifact follows one build through selection, execution, signing, and delivery.
- How Oore chooses pipeline configuration
explains when
.oore.yamlwins over the settings saved in the UI. - How Oore trusts Direct macOS runners explains why creating a project is a trust decision, not a sandbox.
While you ship
- How signing works in Oore explains how the runner signs builds without giving keys to repository code.
- How artifact delivery works connects storage, short-lived download links, and installs on phones.
As the team grows
- How External Access works explains what leaving Local Only changes, and how OIDC and Trusted Proxy compare.
- Oore’s security model separates sign-in, roles, repository trust, and secrets.
- How multiple instances stay separate explains what happens when one browser connects to several backends.
Next step
Start with Which setup do I need? if you have not installed Oore yet.