Environment Templates
Create .env.example-style templates to streamline onboarding and ensure every team member has the required variables.
Creating a Template
Derive a template from an existing environment:
- Open the Vault tab and select the source environment.
- Click Create Template and enter a name (e.g., “Standard Backend Config”).
- Review the variables — the template captures names, descriptions, validation rules, required/sensitive flags, but never actual values.
What a Template Contains
| Included | Not Included |
|---|---|
| Variable names, descriptions, required/sensitive flags, validation rules | Actual values (always blank) |
| Secret file names (as a checklist) | Encrypted file contents |
Applying a Template
- In the Vault tab, click New Environment.
- Select Apply Template and choose a template.
- The new environment is created with all variable entries — values are blank and must be filled in.
Required variables are flagged so users know what to set before the environment is complete.
Template Diff
Compare a template against an existing environment to identify gaps:
- Missing in environment (red) — Variables in the template but not the environment.
- Extra in environment (blue) — Variables in the environment but not the template.
- Matching — Present in both with compatible definitions.
Managing Templates
All templates are listed under the Templates section in the Vault tab. You can add, remove, or update variable definitions, rename the template, or delete it. Changes do not retroactively affect environments already created from it.
Onboarding
Templates drive the onboarding checklist for new team members. When a new member joins, they see all required variables with empty fields to fill in, then download a .env.example or use the CLI to inject values locally.