If I install Magento 2 via composer, I end up with a root level folder named update/

This contains the stand-alone updater application.

Where do the updater come from? I know Magento's composer installer copies a lot of stuff out of the


module, but the update application isn't in this this folder. In fact, none of the files in the update application appear anywhere in vendor folder. (or do they?)

Does anyone know where these files come from, and what puts them on your system when installing Magento via the composer.phar create-project method?

  • I think it was in the project repository itself. So does not have to be copied from vendor. No time to verify for now – David Verholen Nov 9 '17 at 17:40

Full details are in this old article (self link), but here's the high level overview.

When you say

composer create-project --no-install --repository-url=https://repo.magento.com/ magento/project-community-edition my-magento2

you're telling Composer to download the magento/project-community-edition package and drop its contents directly in the my-magento2 folder. In addition to containing the composer.json file with all the Magento 2 packages listed, the magento/project-community-edition package includes the updated application in a top level update folder.

| improve this answer | |

It is part of the project-community-edition zip file. If you look into it (easy to get from composer cache dir), you will see the following:

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.