Problem/Motivation

Since #2788777: Allow a site-specific profile to be installed from existing config a profile crafted for a specific site can be installed from configuration if it includes the configuration as part of the profile. However, this is not yet equivalent to installing any site given its configuration which the Configuration installer project was allowing one to do.

This issue is about figuring out how the installer UI needs to change to allow any site to be installed from configuration.

Proposed resolution

Add options to the Installer UI that allow a user to upload a zip/tarball of an existing config or choose a configuration directory.

Remaining tasks

define new UI elements and workflow, such as possibly adding the UI to either set the config directory or upload the configuration via zip file
agree.
implement.

User interface changes

New installer options.

API changes

none.

Data model changes

none.

Comments

bircher created an issue. See original summary.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

jasonawant’s picture

jasonawant
he/him
Primary language English
Location New Orleans, USA
commented

How is this issue different than #2980670: Install a site from config if the config directory is set in settings.php? In that issue, the installer UI provides an option to install from a configuration directory specified in settings.php?

Does this issue geared toward an alternative w/out specifying config directory in settings.php?

bircher’s picture

bircher
Location 🇨🇿
commented

Yes this is about adding the UI to either set the config directory or upload the configuration via zip file as the config_installer does.

jasonawant’s picture

jasonawant
he/him
Primary language English
Location New Orleans, USA
commented
Issue summary: View changes

thx!

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

frob’s picture

frob
Primary language English
commented
Title: Add option to install from existing configuration to installer » Add options to the installer UI which allow a user to upload a zip with configuration or specify a config directory
Issue summary: View changes

Updated the title so it isn't confused with #2980670: Install a site from config if the config directory is set in settings.php

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

alexpott’s picture

alexpott
he/they
Primary language English
Location 🇪🇺🌍
commented
Version: 8.9.x-dev » 9.1.x-dev
Issue tags: -CMI 2.0 candidate
Parent issue: #1613424: [META] Allow a site to be installed from existing configuration »

Discussed with @bircher while reviewing CMI2. We're not sure that this is a necessary feature so going to punt to 9.1.x and remove from the meta and roadmap - #3008882: Roadmap for CMI 2.

If we're wrong then we can add this back to the roadmap.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.