Skip to content
Docs

basemodo env set

Set Secrets: NAME=value ..., or one NAME alone to read its value from stdin. The App gets them the next time it starts: basemodo restart.

Terminal window
basemodo env set [OPTIONS] <NAME=value>...

All are set or none. Names are letters, digits and , not starting with a digit; PORT and BASEMODO* are Basemodo's.

Arguments

  • NAME=value... (required): The Secrets, each as NAME=value (everything after the first = is the value). In a terminal, one NAME alone reads its value from stdin.
  • --app <APP>: The App whose Secrets to change. Default: the one named after the current folder.

Like every command, it also takes the global options --json and --api-url.

Examples

Set two Secrets:

Terminal window
basemodo env set STRIPE_KEY=sk_live_123 MAILER_TOKEN=abc

Set one from a file, so the value stays out of your shell history:

Terminal window
basemodo env set STRIPE_KEY < stripe-key.txt

Output

With --json, it prints {"secrets": [{"name", "updated_by", "updated_at"}], "changes": [{"name", "action", "by", "at"}]}, never a value.

From an agent

The local MCP serves it as the tool env_set. It changes things, so an agent's client may ask you before it runs. Its arguments are the command's, named as JSON keys: pairs (list of text), app (text). It answers what the command prints with --json.

Explained in