> 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/application-settings.md).

# Application settings

Settings and default configuration for your application's environments

Release deploys your application's code to multiple environments.

We make it quick and easy to create new environments by helping you skip manual configuration every time you create a new environment.

When you create new environments, Release generates each new environment's configuration files from two files in your application's settings:

1. [Application Template](/reference-documentation/application-settings/application-template.md) — the template for each new environment's [Environment Configuration](/reference-documentation/environment-settings/environment-configuration.md).
2. [Environment Variables](/reference-documentation/application-settings/default-environment-variables.md) — the template for each new environment's [Environment Variables](/reference-documentation/environment-settings/environment-specific-environment-variables.md).

![Application Settings](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-dc46d2c46f451c705a2b51afca825fd324bfb380%2Fapplication-settings-main.png?alt=media)

These two files are the starting points for generating environment-specific configuration for each environment you create.

After an environment is created, you can edit the environment's configuration and variables at any time. Environment-specific configuration is useful if, for instance, an environment for a feature branch needs environment variables that don't apply to other branches.


---

# 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/application-settings.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.