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.
Comments
Comment #1
Crell CreditAttribution: Crell commentedI'm generally in favor of un-hard-wiring things and loosening up dependencies, but I am not clear on what's being proposed here. Do you have an example of what you mean?
Comment #2
chx CreditAttribution: chx commentedSure. There is a list of include files and another of modules in install_begin_request(). My thought was that we could check for the existence of a config file, perhaps distribution.yml in the Drupal root which would allow, well, distribution makers to load more files / modules here. If you want to go really far, perhaps we could get away with customizing the theming as well.
Comment #3
Crell CreditAttribution: Crell commentedHm. OK, so we're talking about this for fancier install profiles, rather than as the core control of the installer? I'm OK with that, but I'd rather get the new installer core in place first.
Comment #4
chx CreditAttribution: chx commentedThe new installer is a fantasy that will never get done. IMO. This is something doable.
Comment #4.0
chx CreditAttribution: chx commentedrevised description to represent my current understanding / goals.
Comment #17
smustgrave CreditAttribution: smustgrave at Mobomo commentedWonder with the current state of D10 if this is still a valid task?