Delivery pipeline
ERun's other half. The environment model gives you a namespace per task; the delivery pipeline gives every one of those environments the same way to ship code: build → release → push → deploy. Whatever the stack — a LAMP app on a VM, a Go service, an autoscaling enterprise system — it ships the same way.
Command primitives
ERun's delivery commands are pure primitives: build, push, deploy, and open each do exactly one thing, and the thing that flows between them is a version. Understanding that split is what makes the pipeline predictable — every command is safe to run on its own, and orchestration is something a caller composes on top, not magic hidden inside a command.
Container registries
A project keeps a list of container registries, and each one is marked with the role it plays in the build → copy → deploy flow. One registry is where images are built and pushed; another can be where a cluster pulls from; ERun mirrors images between them on deploy when you ask it to.
Versioning
Every image and chart ERun produces carries a version, and the version tells you two things: what it is (a stable release, a candidate, a throwaway build) and where it's allowed to go. You almost never type a version by hand — ERun generates it from one number in a file plus the branch you're on.