# Configure Environment, Compose File and Resources

> Update environment variables, edit the Compose file, and adjust CPU and memory limits for your Docker Compose App, then deploy your changes.

Source: https://flywp.com/docs/site/docker-compose-apps/configure/

The **Configurations** section in your app's menu includes three pages: **Environment**, **Compose file** and **Resources**. Changes made on any of these pages don't take effect until you deploy them.

## Environment

The **Environment** page lists variables for each service along with their respective **Value** fields.

1. Open your app and navigate to **Configurations** → **Environment**.
2. Update an existing value or add a new variable.
3. Click **Apply the changes**.

![The Environment page with a secret variable hidden and a value masked](https://flywp.com/wp-content/uploads/2026/11/compose-configure-environment.png)

Turn on **Secret** for any variable to hide its value on screen. Click **Reveal** whenever you need to view it. Secret values are never shown in version comparisons.

The page also alerts you to:

- **Used in your compose file but not set**: Variables referenced in your Compose file that don't have assigned values yet.
- **Unused variables of a service**: Variables defined here that aren't referenced by any service.

Use **Undo the change of** to discard an edit before applying it. Click **Remove** to delete a variable.

To configure multiple variables quickly, click **Import .env**. Paste the contents of your `.env` file and review the parsed keys and values before applying them. To save a copy of your variables, use the export options on the same page.

:::note
Environment variable updates take effect on your next deploy. If the last apply failed, your app continues running with its previous values.
:::

## Compose file

The **Compose file** page displays your currently deployed configuration alongside an editor for your next changes.

1. Open your app and navigate to **Configurations** → **Compose file**.
2. Edit the file in the editor.
3. Click **Check File**. FlyWP also checks the file as you type and highlights any issues by line and service name.
4. Click **Deploy** once your file passes validation.

![The Compose file page with its editor and the Check File button](https://flywp.com/wp-content/uploads/2026/11/compose-configure-compose-file.png)

Nothing changes on your server until you trigger a deploy, and FlyWP won't let you deploy a file that fails validation. For a breakdown of validation requirements, see [Compose file rules](https://flywp.com/docs/site/docker-compose-apps/compose-file-rules/).

If you created your app from a GitHub repository, this page displays the connected repository, branch, and Compose file path. FlyWP pulls the file directly from this branch on every deploy.

## Resources

The **Resources** page allows you to customize CPU and memory limits for each service.

1. Open your app and navigate to **Configurations** → **Resources**.
2. Adjust **CPU (cores)**, **Memory (MB)** or **Processes** for any service.
3. Click **Save Limits**.

![The limits table with memory, CPU and processes for each service and the Save Limits button](https://flywp.com/wp-content/uploads/2026/11/compose-configure-resources.png)

FlyWP overrides any limits defined inside your Compose file with these settings. Updates saved here take effect during your next deploy.