mise-env-directives

To load environment variables from a dotenv file in Mise, use the `_.file` directive within your `mise.toml` configuration. This automatically reads and applies vars from `.env`, JSON, or YAML files using `config_root` resolution for accurate local project path mapping.

Yes, Mise supports defining required environment variables with helpful missing messages and allows you to redact secrets for safe logging. This ensures your CI pipelines and multi-project workspaces validate necessary vars without exposing sensitive configuration data.

The best way to extend PATH and source scripts dynamically in Mise is by using the `_.path` and `_.source` directives. These support template rendering and lazy evaluation via tools, ensuring scripts and paths are evaluated only when needed across your multi-project workspaces.

Mise handles plugin-driven env directives using a two-pass evaluation mechanism to ensure tool-provided vars are fully available. This process evaluates plugin-based env configurations before composing the final environment state, preventing missing variable errors during script execution.

Yes, you can manage multiple environment blocks in Mise using the `[[env]]` configuration syntax. This allows you to leverage templates and shell-style expansion to compose the final env state by combining vars loaded from files, scripts, and plugins.

Mise environment variable management is explicitly designed to work across local projects, CI pipelines, and multi-project workspaces. It automates loading, composing, and validating vars from files, scripts, and plugins regardless of your deployment environment.