PHP 7.3 reaches end of support in December 2021 and Adobe Commerce 2.3.x reaches end of support in April 2022. We strongly recommend planning your upgrade now to Adobe Commerce 2.4.x and PHP 7.4.x to help maintain PCI compliance.

Clone the repository

Install Composer

First, check if Composer is already installed:

In a command prompt, enter any of the following commands:

  • composer --help
  • composer list --help

If command help displays, Composer is already installed.

If an error displays, use the following steps to install Composer.

To install Composer:

  1. Change to or create an empty directory on your Magento server.

  2. Enter the following commands:

    1
    
    curl -sS https://getcomposer.org/installer | php
    
    1
    
    mv composer.phar /usr/local/bin/composer
    

For additional installation options, see the Composer installation documentation.

Clone the repo

This section discusses how to get current code by cloning Magento’s GitHub repository and checking out branches. You can either checkout a release branch or a development branch:

  • Release branches, like 2.x.0, are more stable. You must use a release branch with the Data Migration Tool.

  • Development branches, like 2.x-develop, contain the latest changes.

You can checkout a specific release branch after cloning the latest code.

Refer to GitHub’s documentation for instructions on cloning a repository.

Creating an authorization file

The Magento 2 GitHub repository requires you to authenticate. The composer install commands fails if you do not.

Generate Magento and Github keys

To authenticate, you will need to generate Magento authentication keys and a Github personal access token.

Create auth.json

Accessing the Magento 2 GitHub repository requires authentication. The command composer install fails without it. Requirements to authenticate include:

  1. Commerce authentication keys
  2. GitHub personal access token
  3. Composer auth.json file

Create Commerce authentication keys

Follow this guide to create Commerce authentication keys.

Create a GitHub personal access token

The Composer auth file requires the github-oauth property, but do not create a GitHub OAuth App. Create a personal access token instead.

Follow this guide to create a GitHub personal access token.

When choosing token permissions, select all checkboxes in the repo scope. Composer auth does not require other permissions.

Create auth.json file

  1. Log in to your Commerce server as the Commerce file system owner.
  2. Create the auth.json file in the user’s home directory. For example, if magento_user is your Unix username, then create /home/magento_user/.composer/auth.json.

Edit auth.json file

Replace the <placeholder> values with your token and keys:

1
2
3
4
5
6
7
8
9
10
11
{
    "github-oauth": {
        "github.com": "<your GitHub personal access token>"
    },
    "http-basic": {
        "repo.magento.com": {
            "username": "<public key>",
            "password": "<private key>"
        }
    }
}

Related topics

After completing the tasks discussed on this page, see Update installation dependencies.