[bldr]docs
Concepts

Concepts

Every word bldr uses, in a sentence or two each, with a page on the ones worth more.

The whole vocabulary, briefly. Follow a link when a word starts mattering to you, not before.

WorkspaceA directory with a bldr-workspace.yml. The unit you register with a node and build.
MemberOne buildable thing inside a workspace: a directory, a git repository, a container image.
TargetOne thing a member can produce. Your build code declares them; a build picks among them.
BuildOne run of your build code against a workspace, producing the targets you asked for.
ArtifactContent addressed by the hash of its bytes. What every target produces and every step consumes.
PodA container bldr runs a build step in. Content goes in, content comes out.
CacheWhy a build that has nothing new to do does nothing.
RunSomething kept running, backed by a build.
DeploymentA declared step you invoke against what a build produced.
NodeThe daemon that stores content and runs pods. Your machine talks to one; it does the work.
FunctionA named, versioned operation a node knows how to perform, such as pod.dag/v0.0.0. Build code calls them; you rarely name one directly.
RefA name pointing at content, so you can say release instead of a hash.

The shape of it

Five words carry most of the weight, and they nest:

workspace          the directory you build
 └── member        one buildable thing in it
      └── target   one thing that member produces
           ↑
        a build selects targets and produces artifacts
           ↓
     a run or a deployment acts on what came out

Everything else is detail underneath that.

On this page