With Magento 2, composer is supported out of the box. Free extensions can easily be downloaded via public repositories like GitHub. However, for commercial extensions we have decided to setup our own private repository that can be accessed through a subscription URL. This guide explains how to install commercial Magento 2 extensions created by Yireo.
Before I start writing, first of all, big kudos to Alan Storm who wrote an excellent blog where I actually got all of my details from. This guide is mainly meant to extend his post with some further thoughts and practical steps.
More and more Magento 2 projects reach their final stage all across the world. And with that, the question what would be the ideal deployment procedure also pops up. During trainings I have been discussing the right steps over and over again. Even though I do not build shops itself, here's a writeup on what I think would be a proper deployment of Magento 2.
With Magento 2.1, a new class structure has been introduced - dubbed the Entity Manager - which allows for a better structure to work with entities through composition, instead of relying upon parent classes to do the work. Let's see what's inside this new class.
Magento 2 offers a great way of loosely coupling modules together, by using the concept of Dependency Injection with a bit of configuration flavor. When you for instance want to inject yourself with a certain class, you can inject yourself with an instance of the interface by adding this to your constructor. Simple as that. However, make sure that one dependency is not injected twice.
The Yireo_NewRelic2 module for Magento 2 allows you to enhance the information passed on from Magento to the New Relic dashboard. The following guide helps you to install things.
When having installed Magento 2 somewhere, you might encounter the following error in the frontend: We're sorry, an error has occurred while generating this email.. This guide helps you troubleshoot this issue.
Read more: We're sorry, an error has occurred while generating this email.
When Magento 2.0.0.0 was released, it could be either installed using composer or using a ZIP-based install. When Magento 2.0.0.1 was released, the overall advice was to upgrade as soon as possible. However, the composer method failed because of missing dependencies. This short guide tells you how to step from Magento 2.0.0 to 2.0.1 or later using composer.