Magento 2 setup:di:compile – General Question and Answer

magento2setup-di-compile

This is a general question about the magento 2 cli, and what the setup does. Every time i want to install or uninstall a module I have to run the following command.

setup:di:compile

What does this do? Does it take all the new modules and compile them? And what is the difference between this and:

setup:di:compile-multi-tenant

Best Answer

setup:di:compile-multi-tenant

Use this command if you have multiple tenants, which means more than one independent Magento application. In other words:

There is one Magento 2 code base instance

There is one database instance per tenant

Independent configurations in the Magento Admin per tenant

The storefronts are independent of each other

Source: http://devdocs.magento.com/guides/v2.0/config-guide/cli/config-cli-subcommands-compiler.html

Related Solutions

Magento2 – Why Use @media-common in LESS CSS?

Magento 2 follows Mobile First approach and @media-common = true was designed to define styles that are base (mobile) and must be present in styles-m.css. If you drop this declaration styles will be outputted both to styles-m.css and styles-l.css files.

Magento2 – How to Disable setup:di:compile

You don't need to run it. You can simply delete the directories under var/generation (or under generated/ after 2.2). Be careful not to the delete the .htaccess file. You only really ever need to do this when you create a new constructor or change or reorder the arguments being passed into one of your class constructors.

For 2.2 and onwards, Magento documentation suggests using this command:

rm -rf <magento_root>/generated/metadata/* <magento_root>/generated/code/*

Best Answer

Related Solutions

Magento2 – Why Use @media-common in LESS CSS?

Magento2 – How to Disable setup:di:compile

Related Topic