Composer

WIP

BASIC STEPS

Commands to implements : 

composer install --no-dev (offline during CI or live during CD)

drush state:set system.maintenance_mode 1

drush deploy (https://www.drush.org/latest/deploycommand/)

Equals to :

Overview

Taking regular backups of your website is an important step in ensuring the long-term health and stability of your application.

With Drupal, there are a few things to keep in mind when considering your backup approach.

The best-recommended method for handling libraries required by the Contrib modules is through Composer. The Contrib  modules includes a composer.libraries.json file that lists all the required libraries. To install and manage these libraries, you will merge the Contrib composer.libraries.json with your site's composer.json file.

When you are developing or maintaining a contrib project, you may find that the process of modifying code, pushing changes to Drupal.org, and then having Composer update your local environment to pull down what you pushed is tedious and time-consuming. In addition, Drupal.org does not allow history to be rewritten, but if you are developing something experimental you might not want to make your changes final until you've had a chance to test them.

Note: This guide manually sets up Solr in Docker for educational purposes. The recommended and easiest method according to the search_api_solr team is to use the pre-configured Solr solution in DDEV.