burdamagazinorg/thunder-infrastructure

This package is abandoned and no longer maintained. No replacement package was suggested.

Project template for Thunder projects with composer

3.0 2017-05-11 14:42 UTC

Requires

• burdamagazinorg/ad_integration: ~1.0
• burdamagazinorg/hm_newsletter: ~1.0
• burdamagazinorg/robo: ~3.0
• burdamagazinorg/thunder: ~8.2
• composer/installers: ^1.2
• cweagans/composer-patches: ^1.6
• drupal-composer/drupal-scaffold: ^2.2
• drupal/acquia_lift: ~1.0
• drupal/console: ~1.0
• drupal/imagemagick: ~1.0
• drupal/tracdelight: ~1.0
• drush/drush: ^8.1.10
• oomphinc/composer-installers-extender: ^1.1

Requires (Dev)

• behat/mink: ~1.7
• behat/mink-goutte-driver: ~1.2
• drupal/drupal-extension: ~3.0
• jcalderonzumba/gastonjs: ~1.0.2
• jcalderonzumba/mink-phantomjs-driver: ~0.3.1
• mikey179/vfsstream: ~1.2
• phpunit/phpunit: ~4.8
• symfony/css-selector: ~2.8

GPL-2.0+

• Daniel Bosen
• Mladen Todorovic
• Christian Fritsch
• Timo Welde

README

This project template should provide a kickstart for managing your site dependencies with Composer.

If you want to know how to use it as replacement for Drush Make visit the Documentation on drupal.org.

Usage

First you need to install composer.

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.

After that you can create the project:

composer create-project burdamagazinorg/thunder-infrastructure my-project-dir --stability dev --no-interaction

With composer require ... you can download new dependencies to your installation.

cd my-project-dir
composer require drupal/devel:1.*

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.

What does the template do?

When installing the given composer.json some tasks are taken care of:

• Drupal will be installed in the docroot-directory.
• Autoloader is implemented to use the generated composer autoloader in vendor/autoload.php, instead of the one provided by Drupal (docroot/vendor/autoload.php).
• Modules (packages of type drupal-module) will be placed in docroot/modules/contrib/
• Theme (packages of type drupal-theme) will be placed in docroot/themes/contrib/
• Profiles (packages of type drupal-profile) will be placed in docroot/profiles/contrib/
• Downloads Drupal scaffold files such as index.php, or .htaccess
• Creates sites/default/files-directory.
• Latest version of drush is installed locally for use at bin/drush.
• Latest version of DrupalConsole is installed locally for use at bin/drupal.
• Latest version of behat is installed locally for use at bin/behat.
• Latest version ob robo is installed locally for use at bin/robo

Installing Thunder

This project comes with some robo (a Task Runner for php) scripts, which can install and update the site.

To install the site, run ./bin/robo site:install [environment].

• [environment]is local for installations where the database settings are known,
• or devdesktop, if the Acquia DevDesktop is used.
  • In this case, you should Import local Drupal site in the DevDesktop App, before executing the command

If no database dump exists in ./database, the script will install the site, enable the the extensions config and locale, update the locale, export the config and make a database dump.

If a database dump exists, it will just import it.

Updating Thunder

Project update

To update the site, run ./bin/robo site:update [environment]. (Have a look at Installing Thunder to see, what [environment] you need)
This will import the config, apply database and schema updates and update the locale.

File update

This project will attempt to keep all of your Thunder and 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 thunder files.

1. Run composer update burdamagazinorg/thunder
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.

FAQ

Should I commit the contrib modules I download

Composer recommends no. They provide argumentation against but also workrounds if a project decides to do it anyway.

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.

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"
        }
    }
}

How can I prevent downloading modules from thunder, that I do not need?

To prevent downloading a module, that Thunder provides but that you do not need, add a replace block to your composer.json:

"replace": {
    "drupal/features": "*"
}

This example prevents any version of the feature module to be downloaded.