Skip to main content

System Requirements

  • macOS, Linux, or Windows
  • Git 2.25 or later
  • Bash, Zsh, Fish, or PowerShell
  • Windows PowerShell 5.1 or later, for the Windows PowerShell installer
Building from source requires Go 1.27.3 or later.

Release Channels

Entire ships two release channels:
  • stable: the default channel for Homebrew, Scoop, install.sh, and install.ps1
  • nightly: prerelease builds available through Homebrew, install.sh, and install.ps1
Scoop supports the stable channel only. For a nightly install on Windows, use install.ps1.

Install and Update Entire

Choose one installation method. Use the update command in the same tab when you want a newer release.
Install the stable channel:
Or install the nightly channel:
The fully qualified cask name adds the entireio/tap tap for you, so no separate brew tap step is needed.Update the channel you installed:

Install While GitHub Is Unavailable

From v0.12.0 on, release archives are published to install.entire.com as well as to GitHub, and both install scripts download from install.entire.com first. The entire.com/install.sh and entire.com/install.ps1 addresses redirect to GitHub, so during a GitHub outage fetch the scripts from install.entire.com directly:
To skip the script, download an archive for a specific version:
Homebrew and Scoop read their manifests from GitHub and do not work during an outage. go install with an explicit version, such as go install github.com/entireio/cli/cmd/entire@v0.12.1, is served from the Go module proxy and also works.

Verify the Installation

Run:
Entire CLI 0.10.5 prints three lines. The Go version and platform reflect the release and system you installed:
Release archives also include git-remote-entire. Git invokes this helper when a remote uses an entire:// URL. Verify that your shell can find both executables:

Installation and Data Locations

The executable location depends on the installation method: Entire stores repository settings in .entire/settings.json and personal repository overrides in .entire/settings.local.json. See Local, Project, and Global Settings for those files. The CLI also uses these directories for each user: XDG_CONFIG_HOME does not change the Entire config directory. Set ENTIRE_CONFIG_DIR when you need a different location.

Control Update Prompts

Set this variable in scripts, CI, or other environments where the CLI should not prompt for an update:

Shell Completion

Entire generates shell completion scripts for Bash, Zsh, Fish, and PowerShell with entire completion. The steps below cover Bash and Zsh.
Add this command to ~/.bashrc:

Uninstall Entire

Use the command that matches your installation method.
Stable:
Nightly:
Uninstalling the executables does not remove repository settings, checkpoints, or user data. Inspect the paths under Installation and Data Locations before removing data you no longer need.

Review Recent Changes

Read the Entire CLI changelog for changes in each release. Continue to the Quickstart to capture your first checkpoint.