Search by

drupal / config_installer

Drupal-Infrastructure

Use configuration from another Drupal site to install a Drupal instance. Suitable for advanced users.

Package info

git.drupalcode.org/project/config_installer.git

Homepage

Issues

Type:drupal-profile

pkg:composer/drupal/config_installer

Security

Advisories: 0

Aikido package health analysis

Transparency log

Statistics

Installs: 0

Dependents: 19

Suggesters: 0

dev-8.x-1.x 2018-09-08 09:27 UTC

Requires

None

Requires (Dev)

None

Suggests

None

Provides

None

Conflicts

None

Replaces

None

GPL-2.0+ bf69125f99e176104296bb7968add27ffcbdd3e0

Published on Packagist.org on 2026-09-14 17:56 UTC

This package is not auto-updated.

Last update: 2026-09-14 17:56:45 UTC

README

  • Introduction
  • Installation
  • Usage
  • Known issues

Introduction

The Configuration Installer project provides a means to install a Drupal 8 site using existing configuration.

This is not a module, Configuration Installer is an installation profile that loads configuration from a specified folder to 'install' the site. This is not a real installation profile either, it helps to install a real installation profile (e.g. minimal) along with an existing set of configuration.

Installation

Download the archive from the Drupal.org project page (or use Composer).

The folder should be placed in the Drupal website root folder in:

/profiles/contrib

Usage

Install the site like you normally would (e.g. through the UI, using drush or drupal console). Note that it's probably better to install Drupal the first time using the minimal profile. This will avoid conflicts when importing the configuration (e.g. existing entities).

Edit the sites/[yoursite]/settings.php file and add the following line at the bottom if it does not exist yet, or change the existing line to match:

$config_directories['sync'] = '/path/to/folder/with/configuration';

Make sure user running the drush commands has read and write permissions to the folder. If you are installing via the web, the webserver will need read permissions as well.

You can now choose to change any configuration value in the administration user interface (e.g. the site name) or create new configuration (e.g. a content type or a view).

You can export your current configuration via drush:

drush config-export

Make sure to create a backup before dropping all tables from the database.

Then re-install the site with the following command:

drush site-install --verbose config_installer config_installer_sync_configure_form.sync_directory=/path/to/folder/with/configuration --yes

Once Drush completes the installation visit the site to confirm the configuration has been used to install the site.

@TODO: add some (more) tips for install hooks, etc?