This topic describes technologies, knowledge, accounts, and steps to complete when working with your Adobe Commerce on cloud infrastructure code, environments, stores, and sites. If you are not experienced with a technology, links to information and resources are provided below to help get you started.
The following technologies are requirements for developing and deploying your store code:
- Adobe Commerce
- Continuous Integration
- Architectures including Starter or Pro architecture
Below are advanced technologies that you should become familiar with:
- Bitbucket if you need a Git repo
- Fastly for CDN (Content Delivery Network) and caching (based on Varnish)
- GitHub if you need a Git repo
- GitLab if you need a Git repo
- New Relic for performance testing
Adobe Commerce on cloud infrastructure does not support the split database performance solution at this time.
What is Git
Git is the heart of all your code in repositories. Git acts as a version control system through branches from a parent. Multiple developers can work together in personal branches all merging into the same parent. You can work on features at the same time in multiple branches.
If you need help with Git, resource links are provided below.
- Git documentation and videos from the makers of Git
- Git cheatsheet and quick guide from Roger Dudler
- Git video with DevForge to understand how people use the repo and commands with a fun story
To get started with Git, download and install Git on your local.
In addition to Git requirements for valid branch names, Adobe Commerce adds two additional requirements:
/ character is not allowed. Branch names must be case-insensitively unique. In other words, if you have a branch named
CaSe, you cannot create another branch named
To clone the Git repository, use the Secure Shell (SSH) access method. Do not use HTTPS. For a walk through of configuring SSH with your local, see Enable SSH keys.
Supported software and services
Adobe Commerce on cloud infrastructure uses:
- Operating system: Debian GNU/Linux
- Web server: Nginx
- Database: MySQL (MariaDB)
- Content Delivery Network (CDN): Fastly CDN
- Search: Elasticsearch, OpenSearch
You cannot upgrade the software, but you can configure the following services:
- Elasticsearch. Elasticsearch 7.11 and later is not supported for Adobe Commerce on cloud infrastructure.
- OpenSearch. Adobe Commerce and Magento Open Source versions 2.3.7-p3, 2.4.3-p2, 2.4.4 and later support the OpenSearch service.
See System requirements in the Installation guide for recommended versions.
For Staging and Production environments, you use the Fastly CDN module for Magento 2 for CDN and caching services. See Configure Fastly services.
For information about configuring the software versions to use in your implementation, see the following Adobe Commerce on cloud infrastructure configuration files:
Requirements to get started
To get started as a developer in a Adobe Commerce on cloud infrastructure project, you need to set up the following:
repo.magento.comcredentials in your account.
Get a project invitation from the Account Owner or a super user.
Set up a local Docker development environment.
Adobe Commerce on cloud infrastructure environments are Read Only, including all Starter environments and all Pro Integration, Staging, and Production environments. In a local development environment, you write and test code before pushing it to an Integration environment for further testing, followed by deployment to Staging and Production.
In the local development environment, you develop in branches to add modules, extensions, third-party integrations, and configurations. We recommend reading over develop and deploy process for your Starter or Pro plan.
Adobe Commerce on cloud infrastructure deploys the application in Production mode by default.
Adobe Commerce on cloud infrastructure does not support
Before you test any custom code in your local Adobe Commerce environment, you must do all of the following:
For Pro, set the database
auto_increment_incrementto 3 when you generate the Docker configuration file
Test with the correct file permissions in Production mode
Correct permissions only allow write access to
pub/static, pub/media, and
Development and testing
For development and testing, Adobe recommends the following:
Test your site in an Integration (development) and Staging (near-production) environment as you complete modifications
You can enable and test individual features, new extensions, and third-party integrations on different environments before you merge into a single environment.
You can set an environment variable or enter a CLI command for this specific mode.
- Fully test your site in Staging as a merchant and as a customer before deployment to Production
- Set up Fastly and verify that the Fastly Varnish Configuration Language (VCL) is uploaded
- Before you begin the site launch process, submit a support ticket to provide all storefront domains and subdomains for Staging and Production environments. This information is required to provision SSL/TLS certificates for each environment. See Information that you need to launch your site.
- For custom deploy hooks in Integration, submit a Support ticket to add the hooks to the Staging and Production deployment process.
License and authentication requirements
When you purchase a Adobe Commerce on cloud infrastructure subscription, Adobe creates an account for the License Owner and sends an invitation to the License Owner email address with account verification and login instructions. The License Owner has the Account owner role with permission to create user accounts and assign roles for technical staff, consultants, and Adobe partners involved in the code and production of the stores to the project.
To work with and deploy stores, you need the following:
- A Adobe Commerce on cloud infrastructure account already created or created through an invitation
- Project invitation for contributing developers from the Account Owner or a super user
- Authentication keys for each user who contributes to the project
Your Adobe Commerce account must authenticate using any of the following:
- Create your own Cloud account