Book Image

Magento Extensions Development

By : Jérémie Bouchet
Book Image

Magento Extensions Development

By: Jérémie Bouchet

Overview of this book

Magento has been revealed as the best and the most popular open source e-commerce platform in the world, with about 250k+ online stores. Magento 2 is the most recent version of this awesome toolset: every new and modern development techniques are used to offer a real modular approach and powerful architecture. The book will support you in the writing of innovative and complex extensions. Starting from the beginning, we will cover how to set up a development environment that allows you to be really efficient in your functionality writing, including GIT registering and many other development tools. We then move on to provide a large overview of the best practices to scale your module in a high-load environment. After these foundations, you will see how to use test driven-development (TDD) and unit tests to handle your code. We then build a complex extension together, step by step, and internationally-ready. Next, you will find out how to protect the users’ data. Finally, we will take a look a publishing the extension on the new Magento Connect marketplace and how to protect your intellectual property. After you read this book, you will know everything you need to know to become an invaluable extension editor, whether it is for your customers’ needs or for your own requirements.
Table of Contents (16 chapters)
Magento Extensions Development
About the Author
About the Reviewer

Version control and code management

The "best" workflow does not exist and it's why you need to create, develop, and improve yours. Of course, some guidelines exist and they will provide you with a framework of good practices. These standardized models are very similar, so you just need to take advantage of each model and build your own Git workflow.

Usually, we call the main branch master, which represents the trunk of your developments.

Feature branch workflow

This section is an introduction to the specific workflow called "feature branch". It's based on the following branches:

  • Master

  • Develop

  • Feature

  • Release

  • Hotfix

Master branch

This is the first branch your repository will contain and it is the default one. Usually, the branch designates the main trunk of the developments on which the others are based.

Another way of using the Master branch is to reflect the production: a version which is committed on the master exists in the production environment.

Develop branch

We create a Develop branch, reflecting...