binary
A compiled program file that a computer runs directly, as opposed to the source code it was built from.
In more detail
Releases often attach binaries for each operating system so users need not build the program themselves. Binaries are not readable as text, so tools that compare text, such as diff, cannot show what changed inside them.
Examples
go build -o probe . && ./probeIn Terraform: Terraform is distributed as one statically linked binary, so installing it means putting that single file somewhere on your PATH. There is no language runtime or library to install alongside it. Package managers and version managers do exactly this for you.Related terms
- GitHub Releases — A GitHub feature that turns a Git tag into a release page with notes and downloadable files.
- go build — The go subcommand that compiles a package and its dependencies into an executable file and prints nothing when it succeeds.
- static binary — A program file that carries all the code it needs inside it and loads no shared libraries from the machine it runs on.
- compiler — A program that translates source code a person wrote into a form a machine or runtime can execute, checking it for errors on the way.
- artifact — A file produced by a build, such as a compiled program or an image, that is stored and passed on to later steps.
- PATH — An environment variable holding a list of folders the shell searches, in order, to find the program for a command you type.
- language runtime — The software a programming language needs installed to run programs, such as the Python interpreter or Node.js.
- package manager — A tool that installs, updates and removes software together with what it depends on, such as apt on Debian, apk on Alpine or Homebrew on macOS.
- version manager — A tool that keeps several versions of a program installed and switches between them per project.
Taught in
- Conventional Commits — Advanced Git Internals & Distributed Workflows
- Investigating History: blame, bisect And worktree — Advanced Git Internals & Distributed Workflows
- Tags And Releases — Advanced Git Internals & Distributed Workflows
- What Go Is and Why It Matters — Concurrent Systems Programming with Go
- Installing the Go Toolchain — Concurrent Systems Programming with Go
- Your First Program and go run — Concurrent Systems Programming with Go
- The Standard testing Package — Concurrent Systems Programming with Go
- Building Static Binaries — Concurrent Systems Programming with Go
- Shipping in Scratch and Distroless Images — Concurrent Systems Programming with Go
- Containerizing and Testing the Final Build — Concurrent Systems Programming with Go
- Installing Terraform And Meeting The CLI — Infrastructure as Code with Terraform
- Providers And The required_providers Block — Infrastructure as Code with Terraform
- One Hour, No Weights Published — HashiCorp Terraform Associate (004) Exam Prep
- Infrastructure As Code, And One Workflow For Every Platform — HashiCorp Terraform Associate (004) Exam Prep
- Providers: How Terraform Reaches Every API — HashiCorp Terraform Associate (004) Exam Prep
- Reading A Plan, Saving It, Applying It — HashiCorp Terraform Associate (004) Exam Prep
- Verbose Logging: TF_LOG And Friends — HashiCorp Terraform Associate (004) Exam Prep