Composer-enabled Drupal template

This is Pantheon's recommended starting point for forking new Drupal upstreams that work with the Platform's Integrated Composer build process. It is also the Platform's standard Drupal 9 upstream.

Unlike with earlier Pantheon upstreams, files such as Drupal Core that you are unlikely to adjust while building sites are not in the main branch of the repository. Instead, they are referenced as dependencies that are installed by Composer.

For more information and detailed installation guides, please visit the Integrated Composer Pantheon documentation: https://pantheon.io/docs/integrated-composer

Contributing

Contributions are welcome in the form of GitHub pull requests. However, the pantheon-upstreams/drupal-composer-managed repository is a mirror that does not directly accept pull requests.

Instead, to propose a change, please fork pantheon-systems/drupal-composer-managed and submit a PR to that repository.

Docksal powered Drupal 11 With Composer Installation

This is a sample Drupal 11 with Composer installation pre-configured for use with Docksal.

Features:

• Drupal 11 Composer Project
• fin init example
• Using the default Docksal LAMP stack with image version pinning
• PHP and MySQL settings overrides examples

Setup instructions

Step #1: Docksal environment setup

This is a one time setup - skip this if you already have a working Docksal environment.

Follow Docksal environment setup instructions

Step #2: Project setup

1. Clone this repo into your Projects directory

   git clone https://github.com/docksal/boilerplate-drupal11-composer.git drupal11
   cd drupal11
   

2. Initialize the site

   This will initialize local settings and install the site via drush

   fin init
   

   A composer.lock file will be generated. This file should be committed to your repository.

3. Point your browser to

   http://drupal11.docksal.site
   

When the automated install is complete, the command line output will display the admin username and password.

More automation with 'fin init'

Site provisioning can be automated using fin init, which calls the shell script in .docksal/commands/init. This script is meant to be modified per project. The one in this repo will give you a good starting example.

Some common tasks that can be handled by the init script (and other custom commands):

• initialize local settings files for Docker Compose, Drupal, Behat, etc.
• import DB or perform a site install
• compile Sass
• run DB updates, revert features, clear caches, etc.
• enable/disable modules, update variables values

Security notice

This repo is intended for quick start demos and includes a hardcoded value for hash_salt in settings.php. If you are basing your project code base on this repo, make sure you regenerate and update the hash_salt value. A new value can be generated with drush ev '$hash = Drupal\Component\Utility\Crypt::randomBytesBase64(55); print $hash . "\n";'