Quick start install

We use Composer to manage Magento components and their dependencies. Using Composer to get the Magento software metapackage provides the following advantages:

• Reuse third-party libraries without bundling them with source code
• Reduce extension conflicts and compatibility issues by using a component-based architecture with robust dependency management
• Adhere to PHP-Framework Interoperability Group (FIG) standards
• Repackage Magento Open Source with other components
• Use the Magento software in a production environment

You can also download an archive file for a specific version of Magento in either ZIP or TAR format. Installing Magento from an archive lacks the advantages of using Composer. Contributing developers should use the git-based installation method.

Prerequisites

Before you continue, you must do the following:

• Set up a server that meets our system requirements.
• Complete all prerequisite tasks.
• Create and switch to the file system owner.
• Install Composer.
• Obtain authentication keys for the Magento code repository.

Log in as file system owner

Learn about ownership, permissions, and the file system owner in our Overview of ownership and permissions topic.

To switch to the file system owner:

1. Log in to the Magento server as, or switch to, a user with permissions to write to the Magento file system. See switch to the file system owner.

   If you use the bash shell, you can use the following syntax to switch to the file system owner and enter the command at the same time:

   1
   su <file system owner> -s /bin/bash -c <command>
   

   If the file system owner does not allow logins, you can do the following:

   1
   sudo -u <file system owner>  <command>
   

2. To run Magento commands from any directory, add <magento_root>/bin to your system PATH.

   Because shells have differing syntax, consult a reference like unix.stackexchange.com.

   Sample bash shell for CentOS:

   1
   export PATH=$PATH:/var/www/html/magento2/bin
   

   Optionally, you can run the commands in the following ways:

   • cd <magento_root>/bin and run them as ./magento <command name>
   • <magento_root>/bin/magento <command name>
   • <magento_root> is a subdirectory of your web server docroot.

In addition to the command arguments discussed here, see Common arguments.

Get the metapackage

To get the Magento metapackage:

1. Log in to your Magento server as, or switch to, the file system owner.
2. Change to the web server docroot directory or a directory that you have configured as a virtual host docroot.

3. Create a new Composer project using the Magento Open Source or Adobe Commerce metapackage.

   Magento Open Source

   1
    composer create-project --repository-url=https://repo.magento.com/ magento/project-community-edition <install-directory-name>
   

   Adobe Commerce

   1
    composer create-project --repository-url=https://repo.magento.com/ magento/project-enterprise-edition <install-directory-name>
   

   When prompted, enter your Magento authentication keys. Public and private keys are created and configured in your Commerce Marketplace.

   If you encounter errors, such as Could not find package... or ...no matching package found, make sure there are no typos in your command. If you still encounter errors, you may not be authorized to download Adobe Commerce. Contact Magento support for help.

   See troubleshooting for help with more errors.

   Adobe Commerce customers can access 2.4.x and 2.3.x patches two weeks before the General Availability (GA) date. Pre-release packages are available through Composer only. You cannot access pre-releases on the Magento Portal or GitHub until GA. If you cannot find these packages in Composer, contact Adobe Commerce Support.

Example - Minor release

Minor releases contain new features, quality fixes, and security fixes. Use Composer to specify a minor release. For example, to specify the Adobe Commerce 2.4.0 metapackage:

1
composer create-project --repository-url=https://repo.magento.com/ magento/project-enterprise-edition=2.4.0 <install-directory-name>

Example - Quality patch

Quality patches primarily contain functional and security fixes. However, they can also sometimes contain new, backward-compatible features. Use Composer to download a quality patch. For example, to specify the Adobe Commerce 2.3.4 metapackage:

1
composer create-project --repository-url=https://repo.magento.com/ magento/project-enterprise-edition=2.3.4 <install-directory-name>

Example - Security patch

Security patches contain security fixes only. They are designed to make the upgrade process faster and easier.

Security patches use the Composer naming convention 2.3.2-px. Use Composer to specify a patch. For example, to download the Adobe Commerce 2.3.2-p1 metapackage:

1
composer create-project --repository-url=https://repo.magento.com/ magento/project-enterprise-edition=2.3.2-p1 <install-directory-name>

Set file permissions

You must set read-write permissions for the web server group before you install the Magento software. This is necessary so that the command line can write files to the Magento file system.

1
2
3
4
5
cd /var/www/html/<magento install directory>
find var generated vendor pub/static pub/media app/etc -type f -exec chmod g+w {} +
find var generated vendor pub/static pub/media app/etc -type d -exec chmod g+ws {} +
chown -R :www-data . # Ubuntu
chmod u+x bin/magento

Install Magento

You must use the command line to install Magento.

This example assumes that the Magento install directory is named magento2ee, the db-host is on the same machine (localhost), and that the db-name, db-user, and db-password are all magento:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
bin/magento setup:install \
--base-url=http://localhost/magento2ee \
--db-host=localhost \
--db-name=magento \
--db-user=magento \
--db-password=magento \
--admin-firstname=admin \
--admin-lastname=admin \
--admin-email=admin@admin.com \
--admin-user=admin \
--admin-password=admin123 \
--language=en_US \
--currency=USD \
--timezone=America/Chicago \
--use-rewrites=1

You can customize the Admin URI with the --backend-frontname option. However, we recommend omitting this option and allowing the installation command to automatically generate a random URI. A random URI is harder for hackers or malicious software to exploit. The URI displays in your console when installation is complete.

For a full description of the CLI install options, refer to Install the Magento software from the command line.

Command summary

To display a complete list of commands, enter:

1
bin/magento list

To get help for a particular command, enter:

1
bin/magento help <command>

For example,

1
bin/magento help setup:install

1
bin/magento help cache:enable

The following table summarizes the available commands. Commands are shown in summary form only; for more information about a command, click the link in the Command column.

Common arguments

The following arguments are common to all commands. These commands can be run either before or after the Magento software is installed:

Hooray! You’ve completed the quick install. Need more advanced help? Check out our Advanced install guide.