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

# Application Template

How the Release Application Template works

Release automatically generates an Application Template based on the `docker-compose.yml` file from your repository.

The Application Template defines everything a new environment would need to deploy and run your application: services, jobs, which ports to open, hostnames, deployment workflows, and resource limits.

When you create a new environment, Release uses the Application Template as a starting point to generate an [environment configuration](/reference-documentation/environment-settings/environment-configuration.md).

The default Application Template generated by Release rarely requires any editing because it is based on your `docker-compose.yml`.

To view or edit the Application Template, navigate to **App Settings** and click the **Edit** button in the “Application Template” section.

![How to edit the Application Template](https://585411240-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M1neGLLQ0sDXeK6ooSo%2Fuploads%2Fgit-blob-4f13d4403386a3082a26737da1e89f73df626d0e%2Fapplication-template.png?alt=media\&token=1399663e-df33-49ed-9ba2-380c27034610)

{% hint style="info" %}
Changes to the Application Template will not affect *existing* environments. The template is only used to configure new environments.
{% endhint %}

The `environment_templates` section in the Application Template describes differences between your `ephemeral` and `permanent` environment configurations. You will select one of these options when creating new environments.

See the [Application Template Schema Definition](/reference-documentation/application-settings/application-template/schema-definition.md) for a detailed description of each section in the Application Template.


---

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