Deployment — Docker Compose
Run the full Bifrost stack locally with the reference docker-compose.yaml.
The reference docker-compose.yaml brings up the entire stack on one
Docker network, and is the fastest way to see how the pieces fit together
before reasoning about a production, multi-zone layout.
Services
| Service | Image / build context | Role |
|---|---|---|
hyperloop-frontend | built from the frontend app | Web UI |
hyperloop-api | built from the Orchestrator API | REST control plane |
download-minion | built from the Minion worker | Fetches artifacts per ecosystem |
postgres | Bitnami PostgreSQL | Job/schedule/auth persistence |
rabbitmq | RabbitMQ (management image) | Orchestrator ↔ Minion job queue |
nifi | Apache NiFi | The low-side/high-side bridge |
keycloak | Keycloak, realm imported from docker/keycloak/hyperloop-realm.json | OAuth2/OIDC identity provider |
All six run together and talk to each other over one app-network — this
is a single-zone convenience setup for local development, not a
representation of a hardened air-gapped topology (see
Architecture & deployment models for that).
Running it
docker compose up -dBring the stack down (and drop volumes, if you want a clean slate) with:
docker compose down -vA full walkthrough of environment variables, the Keycloak realm import, and what's safe to tear down versus persist is coming as this section matures.
Next steps
For clustered/production deployment, see Deployment — Helm (in progress).