Authentication
The CLI authenticates with a service token. Tokens are minted in the dashboard and never expire silently.
Mint a service token#
In the dashboard, open Account -> Settings -> Service Tokens and click Create token. Pick the access level (read-only or read-write) and an expiry. Copy the token immediately - it is shown once.
Log in#
you@laptop: ~
you@laptop:~$ easyenv auth login --token ee_live_x4f...92aSaved token to keychain.✓ Logged in as [email protected] (acme-engineering)you@laptop:~$ easyenv statusServer https://api.easyenv.ioAccount acme-engineeringPlan Team (3 of 10 workspaces running)
The token is stored in your OS keychain (Keychain on macOS, libsecret on Linux, Credential Manager on Windows). The CLI never accepts an email/password.
Custom server?
Pass
--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:
bash
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. Required when the token has multi-account access. |
Log out#
bash
easyenv auth logout # forget the local token
easyenv auth whoami # show the active token's identity