Authorize your machine

Working on local repositories needs no account at all. To publish a repository to Rinko Hub, or to reach one already hosted there, this machine has to be authorized against your account — once, in a browser.

Prerequisites

nexa installed — see Install the Nexa CLI.
A Rinko Hub account with a redeemed invite code — see Create your account.
A browser on any machine, and the ability to read this terminal's output.

What you'll do

Run one command, approve the request in a browser, and leave this machine holding a credential it can present to Rinko Hub from then on.

Log in

Command

$ nexa login

Expected output

Opening Rinko Hub in your browser...
Visit: https://rinkohub.com/cli/authorize?request=<request-id>&code=ABCD-1234
Code: ABCD-1234
Waiting for approval... (Ctrl+C cancels this request)
Signed in to Rinko Hub (profile: default)
Device: b46c-3ff2-c4e3-057a

What happens

The CLI asks Rinko Hub to start an authorization request and prints a URL and a short code. It then waits. Open the URL in a browser, sign in if you are not already, and you arrive at Approve Nexa sign-in. Confirm that the code shown there matches the one in your terminal before choosing Approve device.

Signing in here uses the email and password you chose on the sign-up form. The terminal never asks for your Rinko Hub password. On a machine with no system keychain it may ask for an encrypted profile fallback passphrase — a local passphrase you make up to protect the credential stored on that machine, not your account password.

Forgot your password? Use the Forgot password? link on the sign-in page, then run nexa login again once you can sign in — Forgot your password? has the steps.

Approving the request in the browser is what completes it: the waiting command notices, records the credential, and prints the profile it authorized along with an identifier for this device. The command exits successfully. Pressing Ctrl+C while it waits cancels the request and authorizes nothing.

Checking the code is the point of it

The code exists so you can confirm that the page you are approving in the browser belongs to the request your terminal made, and not to somebody else's. If the two do not match, do not approve — cancel and run the command again.

Expected result

The terminal reports the profile it authorized and a device identifier, and returns you to a prompt. This machine can now reach the hosted repositories your account has access to.

What authorization grants

The credential is stored on this machine and identifies this machine to Rinko Hub. It carries your account's access and nothing more: authorizing a device does not widen what you can reach, and a repository you cannot see in the browser stays invisible here. It is what nexa publish presents when it creates a repository under your account.

What you can do with a repository still depends on your access to it. An account with read access can bring work in and synchronize it; contributing work back requires write access.

Profiles

Credentials are kept under a named profile. Unless you say otherwise you get one called default, which is the one every hosted command uses — most people never think about this again.

A second profile is useful when one machine legitimately acts as two accounts, such as personal and work identities. Name it when you log in, and again when you use it:

Command

$ nexa login work

Hosted commands take --profile work to use that credential instead of default.

Logging out

Discard this machine's credential:

Command

$ nexa logout

This removes the stored credential for the profile and nothing else. Your repositories, their history, your working contexts and every file in them are untouched — logging out is not a way to lose work. You can authorize the machine again at any time by running nexa login.

Next step

Choose the folder your projects will live in: set up a Development Root.