Guides

The rest of the documentation teaches the path everyone walks: install, set up a Development Root, record a version, sync. These guides go deeper on one subject each, and none of them is a prerequisite for the others. Read the one that matches the problem in front of you.

Available guides

Privacy and file control

How a path is kept private from the people you otherwise share a repository with. Nexa protects a file by encrypting it under a label key rather than by asking a server to refuse a request, so the protection survives having the repository. This guide covers labels, the .nexapolicy file, how to check your own protection, and — the part readers most often get wrong — exactly what remains visible to someone without the key.

Labels, workspaces and .nexapolicy

The developer-facing account of the policy file itself: the version 1 grammar, one authoring file per Development Root, how a global rule and a project rule merge, why precedence is fixed rather than positional, and the rule that stops classified work reaching a workspace it does not belong in. It also covers what a maintainer does from Rinko Hub — creating labels, handing out their keys, and creating or retiring workspaces — and what the website deliberately does not do, which is author path policy.

Working with workspaces

A branch in Nexa holds a set of competing candidates rather than a single pointer, and selecting one does not delete the rest. This guide covers creating a workspace, deriving an independent sibling from one, and choosing between several attempts at the same problem after you have seen them all.

Collaboration

Organizations, teams, members and repository access on Rinko Hub: who can see a repository, who can contribute to it, and how those hosted permissions relate to — and differ from — the encryption-based privacy in the first guide. The two are separate mechanisms, and confusing them is how people over-trust one of them.