Acquia CMS

Generating a composer.json file

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 the current Drupal version.

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:

  1. Creates a new branch from the tag or branch deployed to your production environment.

  2. Deploys this branch to the RA environment.

  3. Generates a composer.json file above the docroot directory, using the following RA Composer template:

    All existing modules are in your /modules folder.

  4. Runs composer install.

  5. Informs you that the generated composer.json branch is ready for testing.


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.