Download the PHP package burdamagazinorg/thunder-infrastructure without Composer
On this page you can find all versions of the php package burdamagazinorg/thunder-infrastructure. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download burdamagazinorg/thunder-infrastructure
More information about burdamagazinorg/thunder-infrastructure
Files in burdamagazinorg/thunder-infrastructure
Package thunder-infrastructure
Short Description Project template for Thunder projects with composer
License GPL-2.0+
Informations about the package thunder-infrastructure
Composer template for Drupal Thunder projects based on drupal-composer/drupal-project
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
withphp composer.phar
(or similar) for your setup.
After that you can create the project:
With composer require ...
you can download new dependencies to your
installation.
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 indocroot/modules/contrib/
- Theme (packages of type
drupal-theme
) will be placed indocroot/themes/contrib/
- Profiles (packages of type
drupal-profile
) will be placed indocroot/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]
islocal
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.
- Run
composer update burdamagazinorg/thunder
- 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
orrobots.txt
. - Commit everything all together in a single commit, so
web
will remain in sync with thecore
when checking out branches or runninggit bisect
. - 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:
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:
This example prevents any version of the feature module to be downloaded.
All versions of thunder-infrastructure with dependencies
burdamagazinorg/hm_newsletter Version ~1.0
burdamagazinorg/robo Version ~3.0
burdamagazinorg/thunder Version ~8.2
composer/installers Version ^1.2
oomphinc/composer-installers-extender Version ^1.1
cweagans/composer-patches Version ^1.6
drupal/acquia_lift Version ~1.0
drupal/console Version ~1.0
drupal/imagemagick Version ~1.0
drupal/tracdelight Version ~1.0
drupal-composer/drupal-scaffold Version ^2.2
drush/drush Version ^8.1.10