Environment variables

Yomia stores environment variables encrypted at rest and write-only: once set, a value is never shown again. You see names, versions and who changed them — not the secrets themselves.

Set and unset

yomia env set web GREETING=hi          # set a variable (restarts the app)
yomia env unset web GREETING           # remove it

Keep secrets out of your shell history by reading the value from stdin:

echo "$STRIPE_KEY" | yomia env set web STRIPE_KEY=-

Load a whole file at once:

yomia env set web --from-file .env.production

Inspect

yomia env list web       # names, versions, who changed them (never the values)
yomia env history web    # change history

Reference another service

Template variables let one service read another's connection details without hardcoding secrets. For example, wire an app to a managed Postgres:

yomia add postgres
yomia env set web 'DATABASE_URL=${{postgres.DATABASE_URL}}'

The reference is resolved at deploy time, so rotating the database password doesn't require editing the app's config.

Next steps

• Databases
• CLI reference