Workflows

Env Files And Export

Supported dotenv files, parser behavior, examples, and export behavior.

Supported filenames

Project imports look for .env, .env.local, .env.development, .env.production, .env.staging, .env.test, and .env.example in a configured order.

Environment mapping

FileEnvironment
.envbase
.env.locallocal
.env.developmentdevelopment
.env.productionproduction
.env.stagingstaging
.env.testtest
.env.exampleexample

Parser behavior

  • Supports KEY=value assignments.
  • Supports export KEY=value syntax.
  • Supports quoted values.
  • Detects empty values.
  • Detects commented variables.
  • Detects duplicate keys.
  • Detects invalid lines.
  • Records line numbers and warnings.
  • Removes inline comments when the # is preceded by whitespace in unquoted values.

Export behavior

  • Selected dotenv files can be exported through a save dialog.
  • Exports can require in-app confirmation before writing.
  • Secret values are resolved from Keychain when exporting the actual env file.
  • Generated .env.example output keeps keys and writes blank values.
  • Export actions create audit entries and project snapshots.