Installation

One command installs both binaries into ~/.es-runtime/bin, checksum-verified: esrun, the server runtime, and esdev, the development toolchain.

Install

curl -fsSL https://raw.githubusercontent.com/Open-Tech-Foundation/ES-Runtime/main/install.sh | bash

irm https://raw.githubusercontent.com/Open-Tech-Foundation/ES-Runtime/main/install.ps1 | iex

Prefer to build from source? See the README.

Just one of them

A server or CI image has no use for the development binary — and esdev is not a deployment target.

# Linux / macOS
curl -fsSL .../install.sh | bash -s -- --only=esrun
curl -fsSL .../install.sh | bash -s -- --only=esdev

# Windows (PowerShell) — `irm | iex` cannot pass arguments, so this is an env var.
$env:ES_RUNTIME_ONLY = 'esrun'; irm .../install.ps1 | iex

Pinning a version

Each binary is released under its own tag and is pinned independently. Latest:

ESRUN_VERSION=0.29.0 ESDEV_VERSION=0.7.0 curl -fsSL .../install.sh | bash

ES_RUNTIME_INSTALL overrides the install prefix.

Upgrade

Each binary updates itself in place — no reinstall needed.

# Downloads the latest release for this platform and replaces the binary.
esrun upgrade
esdev upgrade

They are versioned and tagged separately, so each resolves its own newest release: esrun upgrade never moves esdev, and neither will pick up the other's archive because the release published most recently happened to be the other one's. A binary already current says so and changes nothing.

Uninstall

Delete the install directory and remove it from your PATH.

# Linux / macOS — remove the install dir, then drop the PATH line from your shell profile.
rm -rf "$HOME/.es-runtime"

# Windows (PowerShell) — remove the install dir, then remove it from your user PATH.
Remove-Item -Recurse -Force "$HOME\.es-runtime"