Drupal内容管理系统 v8.8.9.zip

# Drupal Composer Scaffold This project provides a composer plugin for placing scaffold files (like `index.php`, `update.php`, …) from the `drupal/core` project into their desired location inside the web root. Only individual files may be scaffolded with this plugin. The purpose of scaffolding files is to allow Drupal sites to be fully managed by Composer, and still allow individual asset files to be placed in arbitrary locations. The goal of doing this is to enable a properly configured composer template to produce a file layout that exactly matches the file layout of a Drupal 8.7.x and earlier tarball distribution. Other file layouts will also be possible; for example, a project layout very similar to the current [drupal-composer/drupal-project](https://github.com/drupal-composer/drupal-scaffold) template will also be provided. When one of these projects is used, the user should be able to use `composer require` and `composer update` on a Drupal site immediately after untarring the downloaded archive. Note that the dependencies of a Drupal site are only able to scaffold files if explicitly granted that right in the top-level composer.json file. See [allowed packages](#allowed-packages), below. ## Usage Drupal Composer Scaffold is used by requiring `drupal/core-composer-scaffold` in your project, and providing configuration settings in the `extra` section of your project's composer.json file. Additional configuration from the composer.json file of your project's dependencies is also consulted in order to scaffold the files a project needs. Additional information may be added to the beginning or end of scaffold files, as is commonly done to `.htaccess` and `robots.txt` files. See [altering scaffold files](#altering-scaffold-files) for more information. Typically, the scaffold operations run automatically as needed, e.g. after `composer install`, so it is usually not necessary to do anything different to scaffold a project once the configuration is set up in the project composer.json file, as described below. To scaffold files directly, run: ``` composer drupal:scaffold ``` ### Allowed Packages Scaffold files are stored inside of projects that are required from the main project's composer.json file as usual. The scaffolding operation happens after `composer install`, and involves copying or symlinking the desired assets to their destination location. In order to prevent arbitrary dependencies from copying files via the scaffold mechanism, only those projects that are specifically permitted by the top-level project will be used to scaffold files. Example: Permit scaffolding from the project `drupal/core` ``` "name": "my/project", ... "extra": { "drupal-scaffold": { "allowed-packages": [ "drupal/core" ], ... } } ``` Allowing a package to scaffold files also permits it to delegate permission to scaffold to any project that it requires itself. This allows a package to organize its scaffold assets as it sees fit. For example, the project `drupal/core` may choose to store its assets in a subproject `drupal/assets`. It is possible for a project to obtain scaffold files from multiple projects. For example, a Drupal project using a distribution, and installing on a specific web hosting service provider might take its scaffold files from: - Drupal core - Its distribution - A project provided by the hosting provider - The project itself Each project allowed to scaffold by the top-level project will be used in turn, with projects declared later in the `allowed-packages` list taking precedence over the projects named before. The top-level composer.json itself is always implicitly allowed to scaffold files, and its scaffold files have highest priority. ### Defining Project Locations The top-level project in turn must define where the web root is located. It does so via the `locations` mapping, as shown below: ``` "name": "my/project", ... "extra": { "drupal-scaffold": { "locations": { "web-root": "./docroot" }, ... } } ``` This makes it possible to configure a project with different file layouts; for example, either the `drupal/drupal` file layout or the `drupal-composer/drupal-project` file layout could be used to set up a project. If a web-root is not explicitly defined, then it will default to `./`. ### Altering Scaffold Files Sometimes, a project might wish to use a scaffold file provided by a dependency, but alter it in some way. Two forms of alteration are supported: appending and patching. The example below shows a project that appends additional entries onto the end of the `robots.txt` file provided by `drupal/core`: ``` "name": "my/project", ... "extra": { "drupal-scaffold": { "file-mapping": { "[web-root]/robots.txt": { "append": "assets/my-robots-additions.txt", } } } } ``` It is also possible to prepend to a scaffold file instead of, or in addition to appending by including a "prepend" entry that provides the relative path to the file to prepend to the scaffold file. The example below demonstrates the use of the `post-drupal-scaffold-cmd` hook to patch the `.htaccess` file using a patch. ``` "name": "my/project", ... "scripts": { "post-drupal-scaffold-cmd": [ "cd docroot && patch -p1 <../patches/htaccess-ssl.patch" ] } ``` ### Defining Scaffold Files The placement of scaffold assets is under the control of the project that provides them, but the location is always relative to some directory defined by the root project -- usually the web root. For example, the scaffold file `robots.txt` is copied from its source location, `assets/robots.txt` into the web root in the snippet below. ``` { "name": "drupal/assets", ... "extra": { "drupal-scaffold": { "file-mapping": { "[web-root]/robots.txt": "assets/robots.txt", ... } } } } ``` ### Excluding Scaffold Files Sometimes, a project might prefer to entirely replace a scaffold file provided by a dependency, and receive no further updates for it. This can be done by setting the value for the scaffold file to exclude to `false`: ``` "name": "my/project", ... "extra": { "drupal-scaffold": { "file-mapping": { "[web-root]/robots.txt": false } } } ``` If possible, use the `append` and `prepend` directives as explained in [altering scaffold files](#altering-scaffold-files), above. Excluding a file means that your project will not get any bug fixes or other updates to files that are modified locally. ### Overwrite By default, scaffold files overwrite whatever content exists at the target location. Sometimes a project may wish to provide the initial contents for a file that will not be changed in subsequent updates. This can be done by setting the `overwrite` flag to `false`, as shown in the example below: ``` { "name": "service-provider/d8-scaffold-files", "extra": { "drupal-scaffold": { "file-mapping": { "[web-root]/sites/default/settings.php": { "mode": "replace", "path": "assets/sites/default/settings.php", "overwrite": false } } } } } ``` Note that the `overwrite` directive is intended to be used by starter kits, service providers, and so on. Individual Drupal sites should exclude the file by setting its value to false instead. ### Autoload File The scaffold tool automatically creates the required `autoload.php` file at the Drupal root as part of the scaffolding operation. This file should not be modified or customized in any way. If it is committed to the repository, though, then the scaffold tool will stop managing it. If the location of the `vendor` directory is changed for any reason, and the `autoload.php` file has been committed to the repository, manually delete it and then run `composer install` to update it. ## Specifications Reference section for the configuration direct