sitback/presto-project

Presto!-based project template for Drupal 8 projects.

Composer template for Drupal projects with Presto!

This Composer project template provides a kickstart for managing your site dependencies with Composer and the Presto! installation profile., _(*1)

If you want to know how to use it as replacement for Drush Make visit the Documentation on drupal.org., _(*2)

Usage

First you need to install composer., _(*3)

Note: The instructions below refer to the global composer installation. You might need to replace composer with php composer.phar (or similar) for your setup., _(*4)

After that you can create the project:, _(*5)

composer create-project sitback/presto-project my-drupal-site --stability dev --no-interaction

With composer require ... you can download new dependencies to your installation., _(*6)

cd my-drupal-site
composer require drupal/devel:~1.0

The composer create-project command passes ownership of all files to the project that is created. You should create a new git repository, and commit all files not excluded by the .gitignore file., _(*7)

What does the template do?

When installing the given composer.json some tasks are taken care of:, _(*8)

• Drupal is installed in the web-directory.
• The generated composer autoloader in vendor/autoload.php is used instead of the one provided by Drupal (web/vendor/autoload.php).
• Modules (packages of type drupal-module) will be placed in web/modules/contrib/
• Themes (packages of type drupal-theme) will be placed in web/themes/contrib/
• Profiles (packages of type drupal-profile) will be placed in web/profiles/contrib/
• npm and bower assets installed via Composer will be placed in web/libraries/
  • See Asset Packagist for a pacakge listing
• The Presto! profile is installed into the web/profiles/contrib/ directory and set as the default distribution
• Default writable versions of settings.php and services.yml are created.
• A web/sites/default/files directory is created and made writable
• The latest version of drush is installed locally for use at vendor/bin/drush.
• The latest version of the Drupal Console is installed locally for use at vendor/bin/drupal.

Updating Drupal Core

This project will attempt to keep all of your Drupal Core files up-to-date. The project Sitback/presto-project is used to ensure that your scaffold files are updated every time drupal/core is updated., _(*9)

If you customize any of the "scaffolding" files (commonly .htaccess), you may need to merge conflicts if any of your modified files are updated in a new release of Drupal core., _(*10)

Follow the steps below to update your core files., _(*11)

1. Run composer update drupal/core --with-dependencies to update Drupal Core and its dependencies.
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.

Generate composer.json from existing project

With using the "Composer Generate" drush extension you can now generate a basic composer.json file from an existing project. Note that the generated composer.json might differ from this project's file., _(*12)

FAQ

Should I commit the contrib modules I download?

Composer recommends no. They provide argumentation against but also workarounds if a project decides to do it anyway., _(*13)

Should I commit the scaffolding files?

The presto-project plugin can download the scaffold files (like index.php, update.php, …) to the web/ directory of your project. If you have not customized those files you could choose to not check them into your version control system (e.g. git). If that is the case for your project it might be convenient to automatically run the drupal-scaffold plugin after every install or update of your project. You can achieve that by registering @drupal-scaffold as post-install and post-update command in your composer.json:, _(*14)

"scripts": {
    "drupal-scaffold": "DrupalComposer\\DrupalScaffold\\Plugin::scaffold",
    "post-install-cmd": [
        "@drupal-scaffold",
        "..."
    ],
    "post-update-cmd": [
        "@drupal-scaffold",
        "..."
    ]
},

How can I apply patches to downloaded 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., _(*15)

To add a patch to drupal module foobar insert the patches section in the extra section of composer.json:, _(*16)

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