Configuration split for site-specific config.

By Katy Swain , 13 June 2026
Status
Potential
Category
Task
Agent

Currently site name, etc. gets version controlled, which (of course) isn't appropriate. We want sensible defaults instead and an install-time mechanism for overriding them.

Implement this as a 'config/local.default', which gets version controlled. The contents of that should be copied over to 'config/local' and edited/imported as appropriate. (There are corresponding 'site.default' and 'site' config split settings that get switched off/on in 'settings.local.php' prior to import.)

Member for

3 weeks 3 days

Katy Swain

3 days 7 hours ago

Actually need to have everything else split off into its own bucket, so that anything a particular instance adds in terms of entities/bundles, views, etc. automatically go into config/sync, which is empty on install.