Explore using config to unhardwire list of things loaded on install

Created on 14 August 2012, about 13 years ago
Updated 20 July 2023, over 2 years ago

The current install system uses a number of mechanisms to prepare for installation. What if we were to use the configuration system to handle this stage of the process?

Could we simplify the methods that are used early in the process and reduce the number of dependencies that the system requires by doing this?

This seems like an excellent adventure to take.

@TODO
Write code to pull settings from a configuration file to preload Drupal so that dependencies on the DB are satisfied.
Look to eliminate or simply functions that currently require a DB present in the early stages of a Drupal installation.

πŸ“Œ Task
Status

Postponed: needs info

Version

9.5

Component
InstallΒ  β†’

Last updated 3 months ago

No maintainer
Created by

πŸ‡¨πŸ‡¦Canada chx

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΊπŸ‡ΈUnited States smustgrave

    Wonder with the current state of D10 if this is still a valid task?

  • Status changed to Closed: outdated 6 months ago
  • πŸ‡³πŸ‡ΏNew Zealand quietone

    There has been no work on this task for about 13 years and no response to the question made a year ago. It is likely that it is no longer needed or has been implemented. Therefor, closing.

    If there is work to do here, then either re-open the issue and add a comment or open a new issue and reference this one.

Production build 0.71.5 2024