Configure environments

After fully configuring your store, you need to configure your environments. Environments in Cloud for Adobe Commerce include containers with applications, services, and a database to provide a complete system for your Magento 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:

  •—defines how to build and deploy Magento, 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 Magento uses by name and version. For example, this file may include versions of MySQL, PHP extensions, Redis, RabbitMQ, and Elasticsearch. 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 Magento Cloud Commerce.

When you push code changes, the active environment provisions container updates using the YAML configuration files.

Update Pro Staging and Production environment configuration

For Cloud for Adobe Commerce 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 .magento/services.yaml file.
  • Change the configuration for the mounts and disk properties in the file.

Some Pro projects might also require a support ticket to update the route configuration in the routes.yaml file, and the cron configuration in the file.