As part of the Remote Administration (RA) process for non-composer based
websites, Acquia tries to generate a composer.json
file for your codebase
so that it can assist in moving the website to a Composer-built website running
Drupal 9.x or later.
If the composer.json
file conflicts with custom code and repositories, your
development team must resolve the issues.
You should complete all testing and subsequent changes to the file in the
branch you provide to ensure the composer.json
file is compatible with the
codebase. If any issues arise during the testing process, the RA team can
assist in providing recommendations on how to resolve the issues.
The process for generating the composer.json
performs the following
actions:
composer.json
file above the docroot directory, using the
RA composer template
and all existing modules in your /modules
folder.composer install
.composer.json
branch is ready for
testing.Note
The RA automated process leverages the composerize-drupal project to convert an existing site to a properly structured, Composer based site consisting of a composer.json, composer.lock and vendor directory located above the docroot.
For more information on testing and reviewing branches created by RA, see Testing Remote Administration Updates.