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 Adobe Commerce instance, creating and configuring them in your local branch and deploying the settings across your environments.
The following options, tools, and features can be set up and configured in your store:
- 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
- Adobe Commerce B2B module for Business to Business features, Pro plan only
- cron jobs details how to create and configure cron jobs in all environments
- Multiple websites or stores details how to create and configure multi-sites for your store, for example multiple locales including English, French, and Spanish
- Install, manage, and upgrade modules
- Install a theme for your site and store
- Install security extensions including Google reCAPTCHA and Two-Factor Authentication to enhance secure access to the Admin UI and storefront
Configure your deploy: build hooks, services, and routes
After fully configuring your store, you should configure your deployment. This includes specific files to manage builds, deployments, services, and routes:
- .magento.app.yaml configures how the Adobe Commerce application is built and deployed including services, hooks, cron jobs, and more
- routes.yaml configures how Adobe Commerce 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
We also provide integrations with:
- New Relic configuration for application and performance analysis
- Fastly configuration for CDN and caching
- Code collaboration and version control tools (GitHub, Bitbucket, and GitLab) for managing your Git branches and code
We strongly recommend configuring settings, services, and integrations then using specific commands 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.