.profile files

.profile files compose several .env files into a single selectable profile. Selecting a profile merges every listed env, in order — later entries override earlier ones.

Minimal example

@env envs/base.env
@env envs/dev.env
@env envs/mobile-overrides.env
@env envs/tenant-acme.env

Selecting dev-mobile-acme from the env dropdown loads all four files and resolves variables with last-wins ordering.

Directives

Directive	Description
`@env <path>`	Include an `.env` file. Path is relative to the workspace root. Repeat as needed.

Resolution order

For a profile with:

@env base.env
@env dev.env
@env overrides.env

Variables resolve bottom-up: a key in overrides.env wins over the same key in dev.env, which wins over base.env.

Inside each .env, @extends still applies first — @env is the outer composition layer, @extends is the inner one.

Using a profile

Profiles appear in the env selector alongside plain envs, with a distinct stack icon. Click to activate. The selector tooltip shows the merged key list and the source file for every value.

File location

By convention place profiles under envs/profiles/. Any .profile file anywhere in the workspace is picked up automatically.

envs/
  base.env
  dev.env
  prod.env
  overrides-mobile.env
  profiles/
    dev.profile
    dev-mobile.profile
    prod.profile