Authentication
The CLI authenticates with a service token, generated on your profile in the dashboard. A token does not expire; delete it to revoke it.
Mint a service token#
In the dashboard, open your profile (dashboard.easyenv.io/dashboard/profile, or the user menu at the top right), find the Service Token card and click Generate token. The token belongs to you, not to one account: it can do what you can do in every account you belong to, and it works until you delete it. See API authentication for rotating and revoking it.
Log in#
you@laptop:~$ easyenv auth login --token ee_live_x4f...92aLogged in as [email protected] (8d2e...) on https://api.easyenv.ioActive account: 5e1c08f4-...you@laptop:~$ easyenv statusServer: https://api.easyenv.ioAuth: OK ([email protected])Account: 5e1c08f4-...
The CLI checks the token against the API before saving it, writes it to ~/.config/easyenv/config.yaml (mode 0600) and makes your personal account the active one. Leave out --token to be prompted for it with hidden input. The CLI never asks for an email or password.
--server https://... if you are pointing at a staging or self-hosted EasyEnv. The default is https://api.easyenv.io.Select an account#
Many users belong to multiple accounts. Pick the active one:
easyenv account list
easyenv account use <account-uuid>
easyenv account currentEnv vars for CI#
For CI pipelines, skip auth login entirely and pass credentials via env vars. The CLI reads them on every invocation:
| Field | Type | Description |
|---|---|---|
| EASYENV_SERVER | Server URL. Defaults to https://api.easyenv.io. | |
| EASYENV_TOKENrequired | Service token. | |
| EASYENV_ACCOUNT | Account UUID. Overrides the active account; without it, requests go to the one in the config file. | |
| EASYENV_NO_UPDATE_CHECK | Set to 1 to skip the daily check for a newer release. CI runs skip it already. |
Log out#
easyenv auth logout # clear the token from the config file
easyenv auth whoami # show who the active token belongs to