How the pieces fit

kaji is a short chain. Each link makes something the next one uses, which is why the console lists them in this order.

You make

What it is for

A Portage tree

Gentoo’s recipes: for every one of about 20,000 packages, where its source comes from, how to build it and what it needs. A tree of one day gives the versions of that day. kaji provides public ones, so you rarely make your own.

A Portage config

How you want packages built: USE flags, compiler flags, which versions to accept. Optional; without one you get Gentoo’s defaults.

A signing key

A GPG key. Everything kaji builds for you is signed with it, so that whoever installs it later can check it came from you.

A binary repository

A shop-window for what you have built: the packages, signed, kept for the next build to reuse. Others can be only read from, such as Gentoo’s own ready-made packages.

A package build

You name the packages (nginx). kaji plans every dependency and the order to build them in, then builds, in parallel, and puts the result in your repository.

A root filesystem build

The finished packages installed into an empty directory: what will be inside your image or machine. No compiling happens here.

A container build

That directory made into a container image and pushed to a registry.

A container registry

Where images are kept and fetched from. kaji can run one for you.

A package build is the long step. It can take minutes, when most of what it needs is already built or can be taken ready-made, or hours when much has to be compiled. kaji does the work: you can close the browser and come back.

Built once, reused

kaji remembers. When a build asks for a package that your repository already has, with the same version and settings, it is reused, not built again. When a repository you pull from (Gentoo’s, for instance) has it, it is downloaded in seconds instead of compiled in minutes or hours. That is why the first build is the slow one.

What you will see while it works

A running build has a page that updates itself: its status, the plan, a graph of the jobs and their logs (see Follow a build: status, graph and logs). When it succeeds, kaji checks what it made against Gentoo’s security advisories (see Security: vulnerabilities in what you build).