tokens:setup

Show step-by-step instructions for obtaining and configuring the tokens required by SPLENT commands.

Usage

splent tokens:setup

No arguments or options.

Prints instructions for obtaining and setting up the two credentials that SPLENT needs.

Token	Used by
`GITHUB_USER` + `GITHUB_TOKEN`	`feature:release`, `feature:clone`, `feature:versions`, `feature:upgrade`, `feature:search`, `feature:install`, `check:github`
`TWINE_USERNAME` + `TWINE_PASSWORD`	`feature:release`, `check:pypi`

All tokens go in the workspace .env (loaded by the CLI container at startup).

Credential	Where it comes from instead
The SPLENT marketplace token	`splent login`, which stores it per registry in `.splent/credentials.json`. It never goes in `.env`, and it is only needed by `spl:publish`.
A UVLHub API key	Nowhere. There is no longer one to obtain. The marketplace holds a single key for everybody, and reading a model needs no account at all.
`DOCKERHUB_USERNAME` / `DOCKERHUB_PASSWORD`	Set them in `.env` by hand. `product:release` is the only command that publishes an image.

A GitHub Personal Access Token (classic) with repo scope.

How to get it.

Go to github.com → Settings → Developer settings → Personal access tokens → Tokens (classic)
Click Generate new token (classic)
Enable the repo scope (full control of private repos)
Copy the token. It is shown only once

Add to your .env.

GITHUB_TOKEN=ghp_xxxxxxxxxxxxxxxxxxxxxxxxxxxx

A PyPI API token used to publish packages.

How to get it.

Add to your .env.

TWINE_USERNAME=__token__
TWINE_PASSWORD=pypi-xxxxxxxxxxxxxxxxxxxxxxxxxxxx

TWINE_USERNAME is always the literal string __token__, not your PyPI username.

Once the tokens are set, confirm they work.

splent check:github
splent check:pypi