Configure Magento Commerce
The following information walks you through the options for configuring your store on your local and in all environments. You may need to configure files and settings in your local, pushing settings with your code. For specific services, you configure settings directly in Staging and Production environments.
You can set up multiple websites and stores in your Magento instance, creating and configuring them in your local branch and deploying the settings across your environments.
Build hooks, services, and routes
Specific files manage your Magento configurations for builds, services, and routes:
- .magento.app.yaml configures how the Magento application is built and deployed including services, hooks, cron jobs, and more
routes.yaml configures how Magento processes an incoming URL for your Integration environment
services.yaml configures the services you use in your stores and sites including name, version, and allocated disk space
- MySQL service configuration for the database set in services.yaml
- Redis service configuration for a backend caching solution set in services.yaml
- Solr service configuration for search engines supported for Magento Commerce 2.0 set in services.yaml
- Elasticsearch service configuration for searches supported for Magento Commerce 2.1 and later set in services.yaml
- RabbitMQ configuration for a messaging broker set in services.yaml
You should also configure services directly in Staging and Production:
- Fastly for caching and CDN in Staging and Production environments
- PayPal On-Boarding tool provides PayPal payment gateway checkout by connecting to your PayPal merchant account
We also provide integrations with:
- Blackfire Profiler configuration for tracking and investigating issues for bottleneck issues in processes, method calls, queries, loads, and so on
- GitHub for managing your Git branches and code
We strongly recommend configuring settings, services, and integrations then using the
magento-cloud:scd-dump command to manage the configurations. This command exports all of your modified configurations from database values into a file. You add this file to your code repository and push it for deployment across all environments. For details, see Configuration Management.