bragento/magento-composer-installer

Composer installer for Magento modules

Magento Composer Installer

, _(*1)

, _(*2)

, _(*3)

Supported Types:

magento-module
magento-core
magento-theme (currently just the same as magento-module), _(*4)

Core Installer

Installation

to Install the Magento Core require magento/core in your composer.json.
Magento will be copied to the Magento root dir (Default: 'magento'), _(*5)

{
    "require": {  
        "bragento/magento-composer-installer": "~1",  
        "magento/core": "~1.9"  
    },  
    "extra": {  
        "magento-root-dir": "magento"  
    }  
}

Persistent Files

There are several persistent files and directories, that will be backed up and restored after core deployment:, _(*6)

var
media
app/etc/local.xml, _(*7)

You can also define additional Files to be persistent such as local Modules, _(*8)

{
    "require": {  
        "bragento/magento-composer-installer": "~1",  
        "magento/core": "~1.9"  
    },  
    "extra": {  
        "magento-root-dir": "magento",
        "persistent-files": [
            "somefile",
            "app/code/local/Vendor/SomeModule",
            "app/etc/modules/Vendor_SomeModule.xml"
        ]
    }  
}

Module Installer

Install a Module

Just require the Modules in your composer.json., _(*9)

Many composer installable Magento extensions are listed under packages.firegento.com
There is also an example of how to add a composer package directly from a github (or any git) Repository, _(*10)

{
    "repositories": [
        {
            "type": "composer",
            "url": "packages.firegento.com"
        },
        {
            "type": "git",
            "url": "https://github.com/danslo/ApiImport.git"
        }
    ],
    "require": {  
        "bragento/magento-composer-installer": "~1",  
        "magento/core": "~1.9",
        "firegento/magesetup": "~2",
        "danslo/api-import": "~1"
    },  
    "extra": {  
        "magento-root-dir": "magento"  
    }  
}

Change Deploy Strategy

By default, all Modules are deployed by symlink. You can change this behaviour with the config key 'magento-deploystrategy', _(*11)

Possible values are:
symlink
copy
none (will just install the Module but not deploy it to magento root), _(*12)

{ 
    "extra": {  
        "magento-deploystrategy": "copy"  
    }  
}

Overwrite Deploy Strategy per Module

You can also overwrite the Deploy Strategy for specific Modules under the config key magento-deploystrategy-overwrite, _(*13)

{ 
    "repositories": [
        {
            "type": "composer",
            "url": "packages.firegento.com"
        }
    ],
    "require": {  
        "bragento/magento-composer-installer": "~1",  
        "magento/core": "~1.9",
        "firegento/magesetup": "~2"
    },  
    "extra": {  
        "magento-deploystrategy": "symlink",
        "magento-deploystrategy-overwrite": {
            "firegento/magesetup": "copy"
        }
    }  
}

Auto Append Gitignore

You can define that deployed files will be automatically added to .gitignore in magento root, _(*14)

{
    "extra": {  
        "auto-append-gitignore": true
    }  
}

Contributing

make pull requests solely from the develop Branch.
run the tests before making a pull request, _(*15)