Required configuration files
Each module has its own set of configuration files, gathered into the module's etc directory.
Unlike Magento 1, there is no monolithic configuration file in Adobe Commerce and Magento Open Source.
Root directory location
A component's root directory matches the component's name and contains all its subdirectories and files. Based on how you installed Magento, you can put your component's root directory in one of two places:
<Magento install directory>/app: This is the recommended location for component development. You can set up this environment by Cloning the Magento 2 GitHub repository.- For modules, use
app/code. - For storefront themes, use
app/design/frontend. - For Admin themes, use
app/design/adminhtml. - For language packages, use
app/i18n.
- For modules, use
<Magento install directory>/vendor: You will find this location for installations that use thecomposer create-projectto install the Magento 2 metapackage (which downloads the CE or EE code).Magento installs third-party components in the
<Magento install directory>/vendordirectory. But we recommend adding your components to the<Magento install directory>/app/codedirectory. If you add your component to the<Magento install directory>/vendordirectory, Git will ignore it because Magento adds thevendordirectory to the<Magento install directory>/.gitignorefile.
Location of configuration files
Adobe Commerce and Magento Open Source look for configuration information for each module in that module's etc directory. Depending on the needs of your module, you might have the following configuration files at the top level of your module's etc directory:
acl.xmlconfig.xmldi.xmlmodule.xmlwebapi.xml
Additions you make to those configuration files are applied globally to your module.
In addition to those files, a module also has nested configuration directories in the etc directory for any required administration html, frontend, API REST, or API SOAP specific configuration. Additions you make to files in these directories override the settings in the global configuration files for the respective functionality only. That is, if you add a config.xml file to etc/frontend, the settings you make in that file overrides the settings in etc/config.xml for storefront functionality only.
<your module root dir>/etc/adminhtml/<your module root dir>/etc/frontend/<your module root dir>/etc/webapi_rest/<your module root dir>/etc/webapi_soap/
Global vs local
- Configuration files that are in the top level of that module's
etcdirectory are global to that component. - Configuration files placed in subdirectories (
adminhtml,frontend,webapi_rest,webapi_soap) apply only to those respective functional areas.
Requirements
The exact set of configuration files required for your module depends on what your new module does. The required configuration files depend on how you plan to use the module: will the module be manifested on the storefront UI, or in the Admin panel, or as a backend extension that makes a service call? Or all of the above. For example, if your module performs a function in the Admin, you should add any necessary configuration files for those functions to etc/adminhtml/, like:
<your module root dir>/etc/adminhtml/di.xml<your module root dir>/etc/adminhtml/routes.xml
Similarly, if your module changes the UI, you should add the needed configuration files to ~/etc/frontend/. For example:
<your module root dir>/etc/frontend/di.xml<your module root dir>/etc/frontend/page_types.xml
If the module is a service that may call an API, or does some other work that is not manifested in the UI you should add any needed configuration files in the REST and/or SOAP webapi configuration directories, like this:
<your module root dir>/etc/webapi_rest/di.xml<your module root dir>/etc/webapi_soap/di.xml
Keep in mind that you might be able to handle your module's configuration solely with configuration files at the top level of your module's etc directory, but the nested directory is a useful way to keep the configuration neatly compartmentalized.
