Anybuild documentation

Getting Started

Install Anybuild, let it detect your project, and run the complete build pipeline.

Overview

Anybuild detects a project, generates an editable Anybuild definition, evaluates it into a typed plan, builds the required artifacts, and can start the application. The default command runs the combined auto pipeline.

Terminal

anybuild . --start

The first argument is the workspace path. A path with no explicit subcommand is treated as anybuild auto, so the compact command above is equivalent to anybuild auto . --start.

Install

Install the released CLI with the shell installer or Cargo.

Terminal

curl -fsSL https://anybuild.run/install | sh

Terminal

cargo install anybuild-cli

Confirm the binary is available with anybuild --version.

Choose a builder and deploy runner

Command	Builder	Deploy Runner
`anybuild . --start`	Local toolchain	Local process
`anybuild . --docker --start`	Docker	Local process
`anybuild . --wasmer --start`	Local toolchain	Wasmer
`anybuild . --docker --wasmer --start`	Docker	Wasmer

Generated files

Anybuild is the generated Starlark definition. It is yours to edit and includes the detected typed provider configuration.
.anybuild/ contains build state, artifacts, volumes, and runner-specific files.
In a subdirectory project, the definition is named Anybuild.<subdir-slug>.

Legacy Shipit files and .shipit state are renamed automatically when the modern names are absent.