typebase-io-cli env
Manage environment variables on your deployment provider.
Last updated on
Manage environment variables on your deployment provider.
env <target> get <key>
Get an environment variable from your deployment provider.
npx typebase-io-cli env dev get DATABASE_URLnpx typebase-io-cli env prod get BETTER_AUTH_SECRETenv <target> add <key> <value>
Set an environment variable.
npx typebase-io-cli env dev add MY_API_KEY sk-123456npx typebase-io-cli env prod add MY_API_KEY sk-789012Options
| Flag | Description | Default |
|---|---|---|
--provider <provider> | Deployment provider: vercel, cloudflare, or deno | From typebase.json |
--no-encrypted | Store the value unencrypted (encrypted is the default) | Off |
Secret handling differs by provider, and env get does not always return the raw value.
On Vercel, values are stored as encrypted env vars unless you pass --no-encrypted, and env get can return the stored value.
On Cloudflare, Typebase currently stores values as Worker secrets, so env get returns ENCRYPTED instead of the raw secret value.
On Deno Deploy, values are marked as secrets unless you pass --no-encrypted. Non-secret values can be returned by env get, but secret
values may come back as ENCRYPTED.
If env get prints ENCRYPTED, the provider is hiding the raw secret. In that case, manage or inspect the variable in your provider dashboard
or go back to the original source you used when setting it.
Examples
Add an encrypted variable:
npx typebase-io-cli env dev add SECRET_KEY my-secretAdd a non-encrypted variable:
npx typebase-io-cli env dev add PUBLIC_URL https://example.com --no-encryptedGet a variable:
npx typebase-io-cli env dev get SECRET_KEY