[PaaS only]{class="badge informative" title="Applies to Adobe Commerce on Cloud projects (Adobe-managed PaaS infrastructure) and on-premises projects only."}

Configuration files overview

Environments in Adobe Commerce on cloud infrastructure include containers with applications, services, and a database to provide a complete system for your Adobe Commerce application codebase and files.

You can configure application settings, routes, build and deploy actions, and notifications to support your project environments using the following configuration files:

Configuration
Filename
Description
Application
.magento.app.yaml
Defines how to build and deploy Adobe Commerce, including services, hooks, and cron jobs.
Environment
.magento.env.yaml
Centralizes the management of build and deploy actions across all of your environments, including Pro Staging and Production, using environment variables.
Routes
.magento/routes.yaml
Configure caching, redirects, and server-side includes.
Service
.magento/services.yaml
Defines the services Adobe Commerce uses by name and version. For example, this file may include versions of MariaDB, PHP extensions, Redis, RabbitMQ, and Elasticsearch or OpenSearch. You must open a support ticket to push these changes to Pro plan Staging and Production environments.
PHP settings
php.ini
An optional file that can be added to the project. The settings contained in this file are appended to the ones maintained by the cloud infrastructure.

Configuration updates to Pro environments

For Adobe Commerce on cloud infrastructure Pro Staging and Production environments, you can update many configuration options in your local development environment and commit the changes to apply them to these environments. However, you must Submit an Adobe Commerce Support ticket to update the following configuration options:

  • Install or update services in the .magento/services.yaml file.
  • Change the configuration for the mounts and disk properties in the .magento.app.yaml file.
WARNING
Some Pro projects require assistance from Adobe Support to update the route configurations in the routes.yaml file and the cron configurations in the .magento.app.yaml file. Adobe recommends making and validating all YAML configuration changes in an Integration environment first, and then deploying them to the Staging environment.
If your changes are not reflected on Staging sites after redeployment and and no related error messages in the log, you must Submit an Adobe Commerce Support ticket. In the ticket, clearly describe the configuration changes you attempted and attach any updated YAML configuration files in the ticket.
recommendation-more-help
7c2b03ac-000c-497d-aba3-2c6dc720a938