Larger companies usually have multiple people involved in a Magento 2 project, including several developers, project managers, internal customers, end customers and other steakholders.
All these people benefit from a properly maintained and properly running Magento 2 webshop.

To properly maintain the quality of a webshop there's multiple factors in place besides the development process itself, including but not limited to the proper use of version control, project managmeent, release management, unit testing, functional testing and more.

To facilitate this, companies usually use multiple environments to run the project on, which allows developers to efficiently develop code without others constantly being stopped in their tracks while code is still buggy or in active development.

This is where DTAP usually comes into play. This short blog is ment as a technical guide into how to quickly and effectively manage a DTAP environment for your Magento 2 projects.


What is DTAP?

 

DTAP is an abbreviation for "Development, Testing, Acceptation and Production" and resembles the 4 environments which the project takes to ensure new versions of are properly developed and tested without the end users and customers having to worry about unfinished results.


DTAP Best Practises

 

Combining Testing and Acceptation to remove overhead

In small to medium sized team, the Testing and Acceptation server is most likely combined into one environment. This is because there's usually not a party involved who would require a separate Acceptation environment. Therefor a D(TA)P environment is very often just 3 environments.

A situation where 4 environments is used, is when a project team tests on the Testing environment, while other steakholders test on Acceptation prior for a new version to make it to production.

 

Automating deployment to remove human error