Magento 2 and

Composer

Peter Jaap Blaakmeer CTO elgentos @PeterJaap

Ook; mede-organisator MUG050, vrijwilliger Meet Magento, hobbybierbrouwer & bordspellenfanaat

What is composer?

Dependency management in PHP

Why would you use Composer?

What does this have to do with Magento 2?

composer.phar / composer.json / composer.lock

composer.pharBinary used to work with composer

composer.json

require / require-dev / replace

composer.lock

Lockfile created when running composer update

Composer repositories

Packagist (default) http://packages.magento.com/ http://packages.firegento.com/

Set up your own with Satis

Magento 2 Composer repository authentication

Why?

Keeping track of installed extensions Keeping track of extensions purchased through Marketplace

Notifications of new versions! Installing of patches!

How?

Through your magento.com account.

Custom extensions

Why?

Easy installable, updatable and reusable code.

How?

Place each extension in a separate Git repository Add a composer.json that sets the name and dependencies

Add the Git repo link to the main composer.json file Run composer update

Editing composer.json

(and run composer update)

Using composer.phar

Semantic versioning- MAJOR.MINOR.PATCH - works through Git tag - tag every versioned release - never use ‘dev-master’ or similar - semver.org

1.0.2 >=1.0 <2.0

^1.2.3 (equal to >= 1.2.3 < 2.0.0, recommended)

Examples