Environments

The CLI can target multiple DreamLake deployments. It ships with two built-in environments — staging and prod — so you never type their URLs. Each environment keeps its own token; switching never logs you out of the other.

Log into a built-in environment

dreamlake login --env staging
dreamlake login --env prod

No --url / --bss needed — the URLs are baked in. dreamlake login with no --env re-authenticates the active environment, and falls back to prod when nothing is logged in yet.

Switch environments

dreamlake env list           # show logged-in envs (* = active)
dreamlake env use prod       # switch — no URLs, no re-login
dreamlake env remove staging # forget a saved env

Every command then targets the active environment — and so does the Python SDK: switching writes the token and server to ~/.dreamlake, the same files dreamlake-py resolves its connection from. One switch moves both tools. dreamlake profile shows which environment is in effect ([env: prod]).

The * in env list marks the environment your commands will actually hit, not just the last one you selected — if a DREAMLAKE_* env var is overriding the connection, or the files were edited by hand, the star disappears and a note explains why.

Custom / self-hosted environments

Define a custom environment once with its URLs, then switch by name forever:

dreamlake login --env dev \
  --url https://dev-api.example.com \
  --bss https://dev-bss.example.com
dreamlake env use dev

Overrides and storage

Resolution order (high → low): flag → env var → ~/.dreamlake → prod. For one-off commands you can override the active env:

The effective connection lives in two files shared with the Python SDK (all chmod 600):

login and env use always rewrite the token and server together, so the pair can never point at different environments.

~/.dreamlake/auth.yml additionally caches a token per environment — it exists only so env use can switch without a new device-flow login, and is never consulted to answer "what am I connected to":

current: prod
envs:
  staging: { server, bss, auth, namespace, token }
  prod:    { server, bss, auth, namespace, token }

dreamlake logout removes the active environment's token and activates the next saved one (or clears the connection if none is left).