Magento – Magento 2: After using composer to install, can the “update” folder be deleted

composermagento2

After installing Magento 2 using the composer method, the update folder that is used to create the project with remains. I cannot see any reason to keep it after installing the composer dependencies.

Is it safe to delete?

Best Answer

Best way is to make it inaccessible. That way you make sure modules that depend on the update application to be (physically) present, still work.

This can be achieved in 2 different ways:

Make pub your document root (best)
Deny access from update directory

After doing this, it'd be nice to make a module which removes the inaccessible link to the update application in the admin.

Related Solutions

Magento – Install magento via Puppet or Composer

Depends on your deployment infrastructure.

If you already use Puppet, stay with Puppet.

actually looks like a nice default setup, but not enough usage to find proper support

Actually the most common way is still to have magento inside your project vcs and only use composer to install additional modules.

Magento – Error in using composer to install a module in Magento 2.0

In order to install Github packages through composer.json you have to define it as repository like this:

{
    "repositories": [
        {      "url":"https://github.com/firegento/FireGento_FastSimpleImport2.git",
            "type": "git"
        }
    ],
}

if that doesn't work, then open your terminal and enter

composer config repositories.fastsimpleimport2 vcs https://github.com/firegento/FireGento_FastSimpleImport2.git

after that run the require command again.

composer require firegento/fastsimpleimport2

Best Answer

Related Solutions

Magento – Install magento via Puppet or Composer

Magento – Error in using composer to install a module in Magento 2.0

Related Topic