Composer builds allow Acquia Remote Administration (RA) clients to efficiently include various scripts and patches, including post-update builds.
Acquia Automation will update Composer built websites whose repositories conform to the proper architecture and include a fully-functioning composer.json file that builds a Drupal website.
This repository contains sample composer.json files which can be used to start a working Drupal 8 build. Each example file builds on the previous, with the most comprehensive being composer-custom.json.
composer-basic.json: This file installs Drupal core, and the required scaffold and installers packages. This is the bare minimum required for a Drupal site on Acquia hosting.composer-contrib.json: This file adds a few Drupal contrib modules as well as two modules intended for development only.composer-libraries.json: This file builds on the previous two by illustrating how you can use Composer to add third-party dependencies, like libraries, and install them in specific directories (the example is drupal/file_browser).composer-custom.json: Coming Soon.
Please see Acquia Automation: Composer builds for a detailed explanation of each section.
- Either use the already present
composer.jsonfile or copy a composer template file into the top level of your repo, renaming it ascomposer.json. - Add the specific Drupal modules, themes and libraries that your site requires. You may do this by manually adding items to the
requiresection of thecomposer.jsonor running the commandcomposer require drupal/modulename. - Ensure that
drupal-composer/drupal-scaffoldis required beforedrupal/core. - Run
composer installto install all code, vendor directories, etc.
Unless you are using a CI tool, you must commit all generated code to your Acquia repository!