> For the complete documentation index, see [llms.txt](https://docs.release.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.release.com/reference-documentation/environment-settings/environment-specific-environment-variables.md).

# Environment variables

How to create and manage environment variables for a particular environment

When you create an environment, Release creates an [environment configuration](https://github.com/releasehub-com/docs/blob/main/reference-documentation/environment-settings/environment-configuration.md) and [environment variables specific to the environment](/reference-documentation/application-settings/default-environment-variables.md#releases-environment-variables). The environment-specific configuration and environment-specific variables files that dictate an environment's behaviour can be found on the Environment Details page. Click the **Edit** button to modify the environment variables.

![](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-023da3a5bc2b755865e608be91130888dd45fe98%2Fenv-variables.png?alt=media)

There is a single structural differences between the [**"Default Environment Variables"**](/reference-documentation/application-settings/default-environment-variables.md) file and the environment-specific **"Environment Variables"** file:

* The "Default Environment Variables" file groups all the default environment variables in the `defaults` section.
* The environment-specific "Environment Variables" file detailes the environment variables that will be exposed to every container in the `envs` section.

You can import secrets from external secrets managers as environment variables. Find instructions in our [secrets guide](/reference-documentation/environment-settings/environment-specific-environment-variables/secrets.md).

The [`mapping`](/reference-documentation/application-settings/default-environment-variables.md#mapping) and [`services`](/reference-documentation/application-settings/default-environment-variables.md#services) sections are the same in both files and will be carried over from the "Default Environment Variables" file to the "Environment Variables" file. You can edit and delete these sections in the "Environment Variables" file.

The schema for environment-specific environment variables is the same as the ["Default Environment Variables"](/reference-documentation/application-settings/default-environment-variables.md#defaults) file.

Here's an example of a schema for environment-specific environment variables:

```
mapping:
  type: Hash
  description: Maps Release variables to your app's variables
  required: false
defaults:
  type: Array
  description: Default environment variables for your app
  required: true
services:
  type: Hash
  description: Service specific environment variables 
  required: false
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.release.com/reference-documentation/environment-settings/environment-specific-environment-variables.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.