Download the PHP package drupal-composer/drupal-scaffold without Composer
On this page you can find all versions of the php package drupal-composer/drupal-scaffold. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download drupal-composer/drupal-scaffold
More information about drupal-composer/drupal-scaffold
Files in drupal-composer/drupal-scaffold
Package drupal-scaffold
Short Description Composer Plugin for updating the Drupal scaffold files when using drupal/core
License GPL-2.0-or-later
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package drupal-scaffold
drupal-scaffold
DEPRECATED - DO NOT USE
This project is deprecated. Please use drupal/core-composer-scaffold.
If you are still using this plugin because you are on Drupal 8.7.x or earlier, please note that it is possible to use core-composer-scaffold with older versions of Drupal 8. Start with the template project drupal/recommended-project, and then pin to an earlier version of drupal/core-recommended after the initial create-project is done. Note that it's generally easier to remove composer.lock and vendor first when moving back to older versions of Drupal core.
OLD README FOLLOWS
Composer plugin for automatically downloading Drupal scaffold files (like
index.php, update.php, …) when using drupal/core via Composer.
It is recommended that the vendor directory be placed in its standard location at the project root, outside of the Drupal root; however, the location of the vendor directory and the name of the Drupal root may be placed in whatever location suits the project. Drupal-scaffold will generate the autoload.php file at the Drupal root to require the Composer-generated autoload file in the vendor directory.
Usage
Run composer require drupal-composer/drupal-scaffold:dev-master in your composer
project before installing or updating drupal/core.
Once drupal-scaffold is required by your project, it will automatically update
your scaffold files whenever composer update changes the version of
drupal/core installed.
Configuration
You can configure the plugin with providing some settings in the extra section
of your root composer.json.
The source option may be used to specify the URL to download the
scaffold files from; the default source is drupal.org. The literal string
{version} in the source option is replaced with the current version of
Drupal core being updated prior to download.
You can also define source as an array to have fallbacks in case of
any HTTP issues.
With the drupal-scaffold option excludes, you can provide additional paths
that should not be copied or overwritten. The plugin provides no excludes by
default.
Default includes are provided by the plugin:
When setting omit-defaults to true, neither the default excludes nor the
default includes will be provided; in this instance, only those files explicitly
listed in the excludes and includes options will be considered. If
omit-defaults is false (the default), then any items listed in excludes
or includes will be in addition to the usual defaults.
The initial hash lists files that should be copied over only if they do not
exist in the destination. The key specifies the path to the source file, and
the value indicates the path to the destination file.
Limitation
When using Composer to install or update the Drupal development branch, the
scaffold files are always taken from the HEAD of the branch (or, more
specifically, from the most recent development .tar.gz archive). This might
not be what you want when using an old development version (e.g. when the
version is fixed via composer.lock). To avoid problems, always commit your
scaffold files to the repository any time that composer.lock is committed.
Note that the correct scaffold files are retrieved when using a tagged release
of drupal/core (recommended).
Custom command
The plugin by default is only downloading the scaffold files when installing or
updating drupal/core. If you want to call it manually, you have to add the
command callback to the scripts-section of your root composer.json, like this:
After that you can manually download the scaffold files according to your
configuration by using composer drupal:scaffold.
It is assumed that the scaffold files will be committed to the repository, to
ensure that the correct files are used on the CI server (see Limitation,
above). After running composer install for the first time commit the scaffold
files to your repository.
