Download the PHP package specbee/drupal-recommended-starterkit without Composer
On this page you can find all versions of the php package specbee/drupal-recommended-starterkit. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Informations about the package drupal-recommended-starterkit
Drupal Recommended StarterKit
A Drupal StarterKit Project template based out of Drupal Recommended Project and Drupal Composer Template to create Drupal projects with out-of-box required tools and packages to kickstart a project.
What is included
- Drupal core
- Drush 12
- Grumphp(A PHP code-quality tool)
- DDEV
- DotEnv
- Config Sync Without Site UUID
Installation
Create a new project with Composer create project command from dev version.
This will install drupal 10.3.0-beta1
For drupal 10.2.6
run the below command:
For drupal 11.0.0-beta1
run the below command:
Please note: You'll need DDEV 1.23.0 or later. See the documentation if you need to upgrade.
You can update the local development configurations for Local Development in the
.ddev/config.yml
file. For example, to change the project name update the
name
parameter in the configuration file.
Adding Packages
Use composer require
to include and download dependencies for your project.
Adding Libraries
You can manage front-end asset libraries with Composer thanks to the asset-packagist repository. Composer will detect and install new versions of a library that meet the stated constraints.
Using GrumPHP
The package setups code quality checking tools for Drupal project during git commits.
Forcing commit message format
To configure commit message structure, use the git_commit_message task. For example, to enforce the commit message contains the Jira issue ID, use the rule as the following snippet. More options are documented online.
Using DotEnv
You can now add environment variables to your .env
file and it will
automatically be available in the $_ENV
global var.
You can use it in settings.php
, in service providers or in other places
throughout your code. Some examples:
On live environments, you should invoke drush dotenv:dump
every time your
.env
file changes. If you don't, the .env
file will be loaded at every
request, which will decrease the performance of your application.
You can use the drush dotenv:dump
command to get debugging info about the
scanned dotenv files and the loaded variables.
Read the Symfony documentation for more information.
All versions of drupal-recommended-starterkit with dependencies
composer/installers Version ^2.0
cweagans/composer-patches Version ^1.7
drupal/config_sync_without_site_uuid Version ^1.0@beta
drupal/core-composer-scaffold Version ^10.3
drupal/core-project-message Version ^10.3
drupal/core-recommended Version ^10.3
drupal/dotenv Version ^1.2
drush/drush Version ^12.5
ewcomposer/unpack Version dev-master
oomphinc/composer-installers-extender Version ^2.0