Run Broka Community from one compose file.

Get it running

1. Download compose.yml and .env.example into an empty folder. A browser saves the second as env.example, without its dot: rename it back, or fetch both, with their checksums, from a terminal:

   curl -fsSLO "https://broka.dev/download/1.3.3/{compose.yml,.env.example,SHA256SUMS}"

2. Copy .env.example to .env and fill in the secrets. The file says how to generate each one, and which lines must never change on a running installation.
3. Run docker compose up -d. Everything the console needs, PostgreSQL included, is in the file; the Orchestrator applies its schema on first start.
4. Open http://localhost:3000 and create the first administrator.

Check what arrived

Every published file is listed with its SHA-256, and SHA256SUMS holds the same values in the format sha256sum reads. Download it next to the two files and run:

sha256sum -c SHA256SUMS

These sums show the files arrived intact; they do not prove who published them. The two files on this page are not signed, and this page will not claim otherwise. The container images the recipe pulls are: each is signed with Broka’s image-signing key, whose public half is at https://broka.dev/keys/cosign.pub, and carries its software bill of materials (CycloneDX) attested with the same key. With cosign 3 or later, check both before the first start:

for image in broka-ui broka-orchestrator broka-broker; do
  cosign verify --key https://broka.dev/keys/cosign.pub orchestalabs/$image:1.3.3
  cosign verify-attestation --key https://broka.dev/keys/cosign.pub --type cyclonedx orchestalabs/$image:1.3.3 > /dev/null
done

The compose file pins orchestalabs/broka-ui, orchestalabs/broka-orchestrator and orchestalabs/broka-broker at 1.3.3: the Community images, on Docker Hub. It pulls them on first start. Setting up the console and connecting your first cluster are in the documentation.