Rinko Hub
Sign in Sign up
Documentation menu

Install the Nexa CLI

Obtain a working nexa command-line program on your machine, put it on your PATH, and verify that it runs.

The Nexa command-line program is called nexa. It is the only tool you need: it works entirely offline against repositories on your own disk, and the same binary talks to Rinko Hub once you authorize it.

Prerequisites

  • A Rinko Hub account with a redeemed invite code. During the closed beta, downloads are only available to admitted accounts — see Create your account.
  • A Mac with Apple Silicon, or a Linux machine on x86_64 or ARM64.
  • A terminal you are comfortable running commands in.

What you'll do

Download a published build, check it is the file we published, put it where your shell can find it, and confirm it runs. About two minutes.

Install

Take the archive for your platform from the downloads page. It lists a SHA-256 checksum beside each one.

Verify what you downloaded

Computing the checksum yourself and comparing it to the published one is what proves the file you received is the file we published. It is the integrity check these builds carry, so it is worth the ten seconds.

Command 
shasum -a 256 <downloaded-file>

On Linux, sha256sum does the same thing. If the value does not match the downloads page, do not extract the archive — download it again, and if it differs a second time, tell us.

Unpack it and run the installer

Extract the archive and run the nexa inside it with the install subcommand. It places itself under your home directory and links it onto your PATH, so it never needs sudo and never writes into a system directory.

Install 
tar -xzf nexa-macos-arm64.tar.gz
./nexa-macos-arm64/nexa install

The archive expands into a directory named for the platform — nexa-macos-arm64, say — carrying the binary alongside a LICENSE and a README.md. The installer leaves that extracted copy exactly where it found it, so you can delete it afterwards or keep it.

What it builds is precisely the installation nexa update maintains later: each version in its own directory with a pointer at the current one, so an update writes the next version beside this one and moves the pointer rather than overwriting the binary you are running. That shape is internal and may change between releases, which is why it is the installer's job rather than yours.

On macOS, Gatekeeper stays out of the way here

macOS marks files as quarantined based on how they arrived. Downloading with curl and unpacking with tar does not set that mark, so the binary runs normally. If you downloaded through a browser instead and macOS refuses the first run, find nexa in Finder, right-click it and choose Open, and confirm once — that is Apple's own mechanism for approving a binary, not a way around it.

Put it on your PATH

Your shell finds programs by searching the directories listed in the PATH environment variable. The installer puts its launcher in ~/.local/bin, which many Linux distributions already include — macOS does not. nexa install checks and tells you which case you are in; if it reported that the directory is not on your PATH, add it in your shell's startup file:

~/.zshrc or ~/.bashrc 
export PATH="$HOME/.local/bin:$PATH"

A change to a startup file applies to shells started afterwards. Open a new terminal, or re-read the file in the current one, before continuing.

Verify the install

Ask the binary for its version. This is the check that proves both that the install worked and that your shell can find it.

Command 
nexa --version

Expected result

The command prints nexa followed by the version number you downloaded — the same version the downloads page shows — and exits successfully. Seeing it means nexa is installed and on your PATH.

If it did not work

"command not found: nexa" — the shell searched every directory on your PATH and found nothing called nexa. On macOS this is almost always ~/.local/bin missing from PATH. Add it as above, open a new terminal, and try again.

"permission denied" — the extracted nexa is not marked executable, which can happen if the archive was unpacked by something that did not preserve the bit. Run chmod +x nexa-macos-arm64/nexa beside the archive, then run the install line again; the installer sets the bit on the copy it places.

The checksum did not match — download the archive again rather than extracting it. A mismatch means the bytes you have are not the bytes we published, and the difference is not worth guessing about.

Building it yourself

Not yet possible. The Nexa source is not public during the closed beta, so there is no repository to clone and no way to compile the CLI yourself. Source availability is planned; until then the published archives above are the only way to install nexa.

If you are here because you would rather compile a binary than trust one: that is a reasonable position, and it is on the roadmap. It is not available today, and we would rather say so than hand you a command that cannot run.

Next step

With nexa installed, sign this machine in to Rinko Hub: log in with nexa login.