kalamuna / kalaconfig
Provides a base set of configuration and module dependencies for starting new Drupal projects.
Installs: 6 769
Dependents: 0
Suggesters: 0
Security: 0
Stars: 1
Watchers: 25
Forks: 0
Open Issues: 0
Type:drupal-module
Requires
- components/chosen: >=1.8.2
- drupal/admin_toolbar: >=1.18
- drupal/big_pipe_sessionless: >=1.2
- drupal/chosen: >=2.0
- drupal/clean_maintenance: >=1.0
- drupal/components: >=1.0
- drupal/config_filter: *
- drupal/config_split: >=1.1
- drupal/core: ^8.0
- drupal/linkit: >=5.0
- drupal/material_admin: >=1.0
- drupal/pathauto: >=1.0
- drupal/redirect: >=1.0
- drupal/twig_tweak: >=2.0
- kalamuna/autogrow_textarea: >=1.0
- kalamuna/kalastatic: *
README
Kalaconfig provides some configuration and module dependencies for starting new Drupal projects, including three config split environments—dev, test, and live.
Note: This module automatically uninstalls itself immediately after installation. But do not remove it! Composer dependencies are still needed.
Usage
-
Merge the following snippet into your project's
composer.json
file so thatdrupal-library
andcomponent
dependencies install to the correct location:"extra": { "installer-types": ["component"], "installer-paths": { "web/libraries/{$name}": [ "type:component", "type:drupal-library" ] } }
where
web/libraries/
is the path to your libraries directory relative to your project root. Take care not to wipe out any of the existingextra
andinstaller-paths
settings that may already exist in yourcomposer.json
. -
Run
composer require kalamuna/kalaconfig
on your main project. -
Run
composer install
on your main project. -
Turn on your local development environment (e.g.,
vagrant up
to use the built-in DrupalVM) -
Install Drupal with core "standard" installation profile.
-
Remove the
$settings['install_profile'] = 'standard'
line automatically appended tosettings.php
by the Drupal install process. -
Enable this module; it will set up a sane Config Split scheme, automatically export your initial configs, and then uninstall itself.
-
Commit the newly-exported configuration files to your repository, and push them to origin.
-
Use the
config_installer
installation profile to create the sites in all other environments (drush site-install config_installer
).
Notes
You may choose not to install dev dependencies in your production/testing/staging environments (recommended) by using composer install --no-dev
. However, that means the dependencies brought in by Kalaconfig will be missing in those environments. Therefore, you must remember to copy any dependencies provided by Kalaconfig that are needed in those environments into your main project's composer.json require
section.