Since https://www.drupal.org/node/2241059, active configuration is in the database by default.

When you install a new Drupal site, you have a file at sites/default/files/config_.../active/README.txt which states:

If you change the configuration system to use file storage instead of the database for the active Drupal site configuration, this directory will contain the active configuration.

Is it possible to change the default so that config is in the file system at sites/default/files/config_.../active?

If it is no longer possible, then the sites/default/files/config_.../active should no longer exist.

If it is possible, then the text at sites/default/files/config_.../active/README.txt should be changed from:

If you change the configuration system to use file storage instead of the database for the active Drupal site configuration, this directory will contain the active configuration.

to

If you change the configuration system to use file storage instead of the database for the active Drupal site configuration (to do this, go to ABC and click XYZ), this directory will contain the active configuration.

Cheers,

Albert

CommentFileSizeAuthor
#4 2323529_4.patch1.83 KBslashrsm
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

slashrsm’s picture

slashrsm CreditAttribution: slashrsm commented

config.storage.active uses Drupal\Core\Config\DatabaseStorage by default. If you alter it to use Drupal\Core\Config\FileStorage shoud save active config in files. Didn't actually try it but this is how it shoudl work in theory.

alberto56’s picture

alberto56 CreditAttribution: alberto56 commented

Thanks,

I didn't try it yet either, but the current sites/default/files/config_.../active/README.txt makes it sound as if anyone can just switch from the DB to the filesystem easily (I was looking for an option in the GUI). Perhaps a better README might be something like:

Advanced users can change the configuration system to use file storage instead of the database for the active Drupal site configuration (to do this, config.storage.active can be set to Drupal\Core\Config\FileStorage instead of the default Drupal\Core\Config\DatabaseStorage; there is no way to do this in the GUI), this directory will contain the active configuration.

Cheers,

Albert

swentel’s picture

swentel CreditAttribution: swentel commented

Yeah, this readme text can probably be updated. There's more info in settings.php - search for 'Active configuration settings'.

slashrsm’s picture

slashrsm CreditAttribution: slashrsm commented
Category: Feature request » Task
Status: Active » Needs review
FileSize
2323529_4.patch1.83 KB

How about something like this?

TomSherlock’s picture

TomSherlock CreditAttribution: TomSherlock commented

swentel, the information in settings.php regarding 'Active configuration settings', does not supply necessary settings for config.storage.active in the services.yml.

Should such detail be provided in settings.php, or at include a 'pointer' to where this information can be found? Such information does not seem to exist, BTW.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

borisson_’s picture

borisson_
Primary language Dutch
Location Mechelen, 🇧🇪
CreditAttribution: borisson_ as a volunteer commented
Status: Needs review » Closed (outdated)

This is outdated, there is a comment in settings.php about this now.