Reference
Exact surfaces to look up: the CLI command reference, troubleshooting for the errors people actually hit, and the documentation glossary.
Three pages to look things up in. Unlike the rest of the documentation, none of these is meant to be read through — they are organised for finding one answer and leaving.
What is here
- CLI reference — every implemented
nexacommand, with its syntax, arguments, options and behaviour. Generated from a dataset verified against the release binary (nexa 0.1.3), so it cannot drift out of step with the program you are running. Start with the fourteen everyday commands; the advanced surfaces are grouped separately below them. - Troubleshooting — the errors people actually hit
first, what each one means, and the command that resolves it. Includes the two commands
readers most often look for and do not find:
nexa clone, andnexa add. - Documentation glossary — the terms this documentation introduces, and a pointer to the product glossary for everything else.
Note: Terms are defined in the product glossary
The vocabulary of Nexa and Rinko Hub — repository, version, branch, workspace, candidate, selected version, sealed content — lives at /glossary, defined once each. The documentation glossary adds only what that page does not cover.
If you are looking for how something works rather than what it is called, the Core concepts section explains the model, and Workflows covers how it is used day to day.