Local bring-up

This page is the operator-first path for starting CALIBER locally and verifying that the runtime is healthy before you use deeper feature or architecture docs.

At a glance#

1. Full suite path#

Use the full suite when you want the local product as it is usually demonstrated: CALIBER, MLflow, storage, and the surrounding services together.

make setup
make start

Then verify:

• CALIBER UI loads
• login succeeds
• readiness reports a usable local posture

2. Plugin-dev path#

Use the plugin path when you are developing CALIBER itself and want the shorter inner loop.

cd caliber
make install
make dev

Optional frontend dev loop:

cd caliber/caliber-ui
npm install
npm run dev

3. Health and readiness#

After either path, do not assume the runtime is usable just because the process started.

Verify both:

• liveness: /health
• readiness: /ajax-api/2.0/mlflow/caliber/readiness

The readiness endpoint is the meaningful one for operator decisions.

Then move to:

• Health and readiness
• Configuration and provider setup

4. First local login#

The local bootstrap path is only for loopback bring-up. Rotate any insecure bootstrap defaults before exposing the deployment beyond the local machine.

For the deeper trust boundary and scope model, use:

• Platform
• Operations runbook

5. After boot#

Once the system is up, the next doc depends on your job:

• using the product: Choose your CALIBER path
• integrating programmatically: Auth and project scoping
• operating and recovering: Operator troubleshooting, Operations runbook
• validating trust and governance: Trust and governance