The goal of this process is to have Composer manage all the site's contrib modules, contrib themes, core upgrades, and libraries (we'll call this contributed code). These customizations need to be replicated in your new project structure. What makes your site code unique is your selection of contributed modules and themes, and any custom modules or themes your development team has created. In the pantheon.yml file, the api_version: 1 and build_step: true values are required.Īdd the Custom and Contrib Code Needed to Run Your Site Then, add build_step: true to pantheon.yml if it is not already included. Remove any values from pantheon.yml that you prefer to keep listed in. Use Terminus to list all available updates: This folder will contain two subdirectories that you'll create in the next sections, one for the site on the former platform, and one for the Pantheon site. In this example, the site name is anita-drupal.Ĭreate a new folder to use while working on the migration. Refer to the Trusted Host Setting documentation for more information. The site owner should ensure the trusted host setting is up-to-date. Pantheon support is not available to users who avoid the Multidev steps. This guide is written for users with access to Pantheon's Multidev feature. The site does not use another package and library manager like Ludwig. Refer to the documentation on Serving Sites from the Web Subdirectory for information about nested docroots. The process outlined in this guide will not work if the site repository has a /web folder at its root. The site cannot be set to use an empty upstream. Will This Guide Work for Your Site?Ĭonfirm that your site meets the following requirements before you continue: The drupal-composer-managed Integrated Composer upstream works with all versions of Drupal, and following the drupal-composer-managed upstream will help keep your site up to date with any general configuration changes recommended by Pantheon.Īdd Drupal core dependency instructions to drupal/core-recommended, to keep the site on the current version of Drupal until you are ready to upgrade to the latest version of Drupal. Switch to the drupal-composer-managed Integrated Composer upstream. Remove dependencies that Composer will manage from the existing Drupal site's Git repository, and have Composer manage those dependencies instead. Overviewĭrupal sites on Pantheon have Integrated Composer built-in to manage site dependencies. If this is not your scenario, see Drupal Migration Guides for additional upgrade paths. Finally, after testing and confirming everything looks good, you'll use Terminus to switch the site over to the new upstream. When everything is working correctly in the Multidev environment, you'll deploy the changes to the Dev environment by replacing your site's master branch with the new branch you've created. You'll then re-add the contrib and custom code for your site to the new branch, and test it on a Multidev environment. In this guide, we'll convert a standard Drupal site to use Composer to manage deployments and dependencies, then switch from drops-8 to the new Integrated Composer drupal-composer-managed upstream while remaining on the current version of Drupal.ĭuring this process, you will create a new branch based on the Git history of the new upstream.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |