---
title: blossom env_var:pull
url: "/docs/reference/cli/env_var/pull/"
canonical_url: https://docs.blossom88.com/docs/reference/cli/env_var/pull/
markdown_url: https://docs.blossom88.com/docs/reference/cli/env_var/pull.md
summary: Write an Environment's variables to a .env file
categories:
- cli
- reference
---

# blossom env_var:pull

Write an Environment's variables to a .env file

## Usage

    blossom env_var:pull --environment ENVIRONMENT [--file FILE] [--force]

## Flags

| Flag | Description |
| --- | --- |
| `--environment, -e (required)` | Environment id to pull from |
| `--file` | Dotenv file to write. Default: .env.<environment name> |
| `--force, -f` | Overwrite an existing file |

Examples:

    blossom env_var:pull --environment environment-100
    blossom env_var:pull --environment environment-100 --file .env.production --force

Writes an Environment's variables to a local dotenv file, by default
`.env.<environment name>`, so a teammate or a new machine can start from
Blossom's copy. The file holds real values, so the command refuses to
overwrite an existing file without `--force`, writes it readable by you
only, and refuses a path that git tracks.

The file groups variables into a `# blossom:build` block followed by a
`# blossom:runtime` block, with keys alphabetized within each block. Empty
blocks are omitted. Each marker applies until the next marker, preserving
Build settings for a later `env_var:push`. Build variables are also available
at runtime. Terminal output names keys only.