No Description http://encyclopediedelaparole.org
Bachir Soussi Chiadmi 7e4794aec1 expo: fixed audio player width for 1280 w screen | 4 years ago | |
---|---|---|
config | 4 years ago | |
drush | 5 years ago | |
scripts | 5 years ago | |
web | 4 years ago | |
.editorconfig | 6 years ago | |
.env.example | 5 years ago | |
.gitattributes | 6 years ago | |
.gitignore | 5 years ago | |
.gitkeep | 5 years ago | |
.travis.yml | 5 years ago | |
LICENSE | 5 years ago | |
README.md | 5 years ago | |
composer.json | 4 years ago | |
composer.lock | 4 years ago | |
load.environment.php | 5 years ago | |
phpunit.xml.dist | 5 years ago |
This project template provides a starter kit 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.
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:
composer create-project drupal-composer/drupal-project:8.x-dev some-dir --no-interaction
With composer require ...
you can download new dependencies to your
installation.
cd some-dir
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.
When installing the given composer.json
some tasks are taken care of:
web
-directory.vendor/autoload.php
,
instead of the one provided by Drupal (web/vendor/autoload.php
).drupal-module
) will be placed in web/modules/contrib/
drupal-theme
) will be placed in web/themes/contrib/
drupal-profile
) will be placed in web/profiles/contrib/
settings.php
and services.yml
.web/sites/default/files
-directory.vendor/bin/drush
.vendor/bin/drupal
.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 modified files are updated in a new release of Drupal core.
Follow the steps below to update your core files.
composer update drupal/core webflo/drupal-core-require-dev "symfony/*" --with-dependencies
to update Drupal Core and its dependencies.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
.web
will remain in
sync with the core
when checking out branches or running git bisect
.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.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.
Composer recommends no. They provide argumentation against but also workrounds if a project decides to do it anyway.
The drupal-scaffold 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 @composer drupal:scaffold
as post-install and post-update command in your composer.json:
"scripts": {
"post-install-cmd": [
"@composer drupal:scaffold",
"..."
],
"post-update-cmd": [
"@composer drupal:scaffold",
"..."
]
},
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 or local path to patch"
}
}
}
Follow the instructions in the documentation on drupal.org.
This project supports PHP 5.6 as minimum version (see Drupal 8 PHP requirements), however it's possible that a composer update
will upgrade some package that will then require PHP 7+.
To prevent this you can add this code to specify the PHP version you want to use in the config
section of composer.json
:
"config": {
"sort-packages": true,
"platform": {
"php": "5.6.40"
}
},