After fully configuring your store, you need to configure your environments. 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:
.magento.app.yaml—defines how to build and deploy Adobe Commerce, including services, hooks, and cron jobs.
.magento.env.yaml—centralizes the management of build and deploy actions across all of your environments, including Pro Staging and Production, using environment variables.
.magento/routes.yaml—configure caching, redirects, and server-side includes.
.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.ini—an optional file that can be added to the project. The settings contained in this file are appended to the ones maintained by Adobe Commerce on cloud infrastructure.
When you push code changes, the active environment provisions container updates using the YAML configuration files.
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 a Support ticket to update the following configuration options:
- Install or update services in the
- Change the configuration for the
diskproperties in the
Some Pro projects require a support ticket to update the route configuration in the
routes.yaml file and the cron configuration in the
.magento.app.yaml file. Adobe recommends updating and testing YAML configuration files in an Integration environment, then deploying changes to the Staging environment. If you discover that your configuration changes are not applied to Staging sites after you redeploy and do not see any related error messages in the log, then you MUST submit a Support ticket that describes the attempted configuration changes. Include any updated YAML configuration files in the ticket.