Automatically generating a composer.json file

When requested, or at the suggestion of the Remote Administration (RA) team, Acquia can attempt to generate a composer.json file for your codebase to assist in moving to a Composer-built Drupal 8 website.

For Standard RA customers, Acquia will use an automated process to provide the branch with the composer.json file in place in the RA environment.

For Premium RA customers, the RA team can assist in modifying and troubleshooting the composer.json file for the purposes of security updates. If the composer.json file conflicts with custom code and repositories, these issues will need to be resolved by your development team.

All testing and subsequent changes to the file should be completed in the provided branch by the customer to ensure that the composer.json file is compatible with the codebase. If issues are raised by the customer during the testing process, the RA team can assist in providing recommendations on how these should be resolved.

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, using the RA composer template and all existing modules in your /modules folder.
  4. Runs composer install.
  5. Informs you that the generated composer.json branch is ready for testing.

For more information on testing and reviewing branches created by RA, see Testing Remote Administration Updates.

Contact supportStill need assistance? Contact Acquia Support

Acquia: Think Ahead

53 State Street, 10th Floor
Boston, MA 02109
United States
Phone: 888-922-7842

Map: Google Maps
View other locations