Skip to main content
Environment variables are how your app gets secrets (API keys, database URLs) without baking them into your source code. Nometria encrypts all variables at rest and injects them at runtime.

​
Add environment variables

On the configuration screen before your first deploy, scroll to Environment Variables and add your key/value pairs.

​
Common variables by framework

Vite exposes variables prefixed with VITE_ to the browser bundle. Never put secret keys in VITE_ variables — use them only for public anon keys or public URLs.

​
Environments

Nometria supports separate variable sets for staging and production:
  • Staging — your *.nometria.com URL or a staging.yourcompany.com subdomain
  • Production — your primary custom domain
Variables set at the project level apply to both. Override individual variables per environment:
  1. Settings → Environment Variables → toggle Per-environment override
  2. Set the staging value and production value separately
This lets you use test Stripe keys on staging and live keys on production with zero code changes.

​
Security

  • All variables are encrypted at rest using AES-256
  • Variables are never logged in build output or deploy logs
  • Values are masked in the dashboard after saving (you can only overwrite, not view)
  • Variables are injected as true environment variables at container startup — they are not written to disk
Never commit secrets to your Git repository. Nometria reads secrets from the encrypted variable store, not from .env files in your repo.

​
Importing from .env files

If you have a local .env file, you can bulk-import it:
  1. Settings → Environment Variables → Import .env
  2. Paste the contents of your .env file
  3. Review the parsed variables and click Import
Nometria strips any # comments and blank lines automatically.