> 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-configuration.md).

# Environment configuration

Each environment has its own specific configuration that is created by combining the default value in the [Application Template](/reference-documentation/application-settings/application-template.md) with any changes or overrides from the template your environment is based on.

![View/edit the environment specific configuration](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-beecaa64763526e0cd644d24a079a933d754d126%2Fview-env-config.png?alt=media)

There are only a few structural differences between the default [**Application Template**](/reference-documentation/application-settings/application-template.md) and the **Environment Specific Configuration** found on the Environment Details page.

* The `environment_templates` stanza in the default configuration highlights the differences between your ephemeral and permanent environments. When you create an environment, Release uses your template and defaults to generate an environment-specific configuration.
* The `datasets` keyword can be included at the root of your environment-specific configuration, unlike in the Application Template. You can add and remove datasets for this particular environment.

Once you create an environment, it has an environment specific-configuration file. All deployments will be based on this file. Changes in the default configuration (Application Template) will **NOT** change the file going forward.

If you would like an environment to pick up changes in the default configuration, you need to delete the current file and make a new one. (Or just make a new file.) This makes it clear where changes to the current specific environment come from.


---

# 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-configuration.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.