ThinkShout's project template for Drupal 8 projects with composer



Drupal Project (Pantheon edition)

Note: This project was forked from the drupal-project repository.

Development set-up

This is a Drupal 8 site built using the robo taskrunner. As such, it does not require separate /project and ~/Sites folders. Install the repo directly into ~/Sites using git clone and you will be ready to begin.

First you need to install composer.

brew install composer

Next add ./vendor/bin to your PATH, at the beginning of your PATH variable, if it is not already there.

Check with: echo $PATH

Update with: export PATH=./vendor/bin:$PATH

Add the custom git repo to your list of available composer paths by opening (or creating) ~/.composer/config.json and adding these lines:

    "config": {
    "repositories": [
            "type": "vcs",
            "url": ""


Start inside the ~/Sites directory and build your site (replace 'some-dir' with the name of the project folder):

composer create-project thinkshout/drupal-project:8.x-pantheon-dev some-dir --stability dev --no-interaction

Start inside the ~/Sites/SITE directory you cloned (you may have named it something other than "SITE")

Get the all the dependencies and modules with:

composer install

Running the robo configure command will read the .env.dist, cli arguments and your local environment (DEFAULT_PRESSFLOW_SETTINGS) to generate a .env file. This file will be used to set the database and other standard configuration options. If no database name is provided, the project name and the git branch name will be used.

robo configure
# Use an alternate DB password
robo configure --db-pass=<YOUR LOCAL DATABASE PASSWORD>

The structure of DEFAULT_PRESSFLOW_SETTINGS if you want to set it locally is:



Running the robo install command will run composer install to add all required dependencies and then install the site and import the exported configuration.

robo install


Test are run automatically on CircleCI, but can be run locally as well with:

robo test

Updating contributed code

Updating contrib modules

With composer require drupal/{module_name} you can download new dependencies to your installation.

composer require drupal/devel:8.*

Applying patches to contrib modules

If you need to apply patches (depending on the project being modified, a pull request is often a better solution), you can do so with the composer-patches plugin.

To add a patch to drupal module "foobar" insert the patches section in the extra section of composer.json:

"extra": {
    "patches": {
        "drupal/foobar": {
            "Patch description": "URL to patch"

Updating Drupal Core

This project will attempt to keep all of your Drupal Core files up-to-date; the project drupal-composer/drupal-scaffold is used to ensure that your scaffold files are updated every time drupal/core is updated. If you customize any of the "scaffolding" files (commonly .htaccess), you may need to merge conflicts if any of your modfied files are updated in a new release of Drupal core.

Follow the steps below to update your core files.

  1. Run composer update drupal/core.
  2. Run git diff to determine if any of the scaffolding files have changed. Review the files for any changes and restore any customizations to .htaccess or robots.txt.
  3. Commit everything all together in a single commit, so web will remain in sync with the core when checking out branches or running git bisect.
  4. In the event that there are non-trivial conflicts in step 2, you may wish to perform these steps on a branch, and use git merge to combine the updated core files with your customized files. This facilitates the use of a three-way merge tool such as kdiff3. This setup is not necessary if your changes are simple; keeping all of your modifications at the beginning or end of the file is a good strategy to keep merges easy.