env:list

List variables defined in the active .env file, grouped by category.

Usage

splent env:list [FILTER] [--keys-only] [--no-mask] [--unset]

Argument / Option	Description
`FILTER`	Optional. Show only variables whose name contains this string (case-insensitive).
`--keys-only`	Print variable names only, one per line. Useful for scripting.
`--no-mask`	Show sensitive values in plain text instead of masking them.
`--unset`	Show only variables that are defined in `.env` but not currently set in the process environment.

Examples

List everything:

splent env:list

Show only GitHub variables:

splent env:list GITHUB

Check what is still missing from the environment:

splent env:list --unset

Get variable names only (for scripting):

splent env:list --keys-only

Example output

  SPLENT
    ✔ SPLENT_APP        sample_splent_app
    ✔ SPLENT_ENV        dev

  GitHub
    ✔ GITHUB_USER       splent-dev
    ✔ GITHUB_TOKEN      ghp_****02

  PyPI
    · PYPI_TOKEN        pypi-****0b

  Database
    ✔ DB_HOST           db
    ✔ DB_NAME           sample_splent_app
    ✔ DB_PASSWORD       ****

  Other
    ✔ REDIS_URL         redis://redis:6379/0

  12 variable(s) in /workspace/.env  (sensitive values masked)

Status indicators

Each line shows a one-character indicator:

Symbol	Meaning
`✔`	Variable is set in the current environment and matches the `.env` value.
`≠`	Variable is set in the current environment but its value differs from `.env`.
`·`	Variable is defined in `.env` but not set in the current environment.

Description

Reads /workspace/.env and groups variables by well-known prefix categories (SPLENT_, GITHUB_, PYPI_, DB_, REDIS_, MAIL_, AWS_, CELERY_). Variables that do not match any category are listed under Other.

Sensitive keys — those containing TOKEN, SECRET, PASSWORD, KEY, PWD, or PASS in their name — are masked by default. Use --no-mask to reveal the actual values.

Difference from env:show

	`env:list`	`env:show`
Output style	Grouped by category	Flat, line by line
Primary use	Quick daily overview	Diagnosing load vs. file mismatches
Filtering	`FILTER` argument, `--unset`	—
Scripting support	`--keys-only`	—

Use env:show when you need to diagnose why a variable is not behaving as expected. Use env:list for a clean snapshot of what is in your .env.