Administrator token

Usage Prepare cloud migration

Manage

Loading…

Projects

Devices

Machines whose agent delivers usage

Project ids: The agent on each machine tags usage with a project id from its configuration. The catalog gives an id a name, a company and its repositories; usage itself is kept by id, so renaming changes no figures.

Device tokens: A device's token is shown once, when the device is added or given a new token; the ledger keeps only its hash. A new token replaces the old one at once and keeps the device's id, so usage the agent sends again is still recognised. If a token is lost, issue a new one.

Revoking a device: The device's token stops working at once. Its agent stops at its next delivery and keeps unsent usage on the machine. Usage already stored stays in every report. Re-enabling issues a new token for the same device; the agent delivers again once restarted with it.

Edit project

Project id

Name Company (optional) Repositories (one address per line, at most 20)

Revoke ?

Its token stops working now. The agent stops at its next delivery.
Usage it has not sent stays queued on the machine.
Usage already stored stays in every report.
To let it deliver again, choose Re-enable: it issues a new token for the same device.

Add a device

The ledger issues a token for the device's agent. Usage it delivers is listed under this name.

Name

Token for

Shown only now. The ledger keeps only its hash; if it is lost, issue a new one.

Device token

On the device, save the token alone in a file such as ~/.config/ai-usage-ledger/device-token and chmod 600 it.
Point server.token_file in the agent's configuration at that file.
Restart the agent. Its next delivery uses the new token.