Weave Code
Composite Config Laravel Package
cartalyst/composite-config
Composite Config is a Cartalyst package for merging and layering configuration from multiple sources into a single composite config repository, letting PHP applications organize, override, and resolve settings cleanly. A small utility aimed at developers who need flexible config composition.
cartalyst/composite-config is a Laravel/PHP package for building composite configuration from multiple config sources. It lets you split settings across files or packages and merge them into a single, predictable configuration tree—keeping large applications organized without duplicating values.
- Merge multiple config files, namespaces, or sources into one config tree
- Support layered defaults and environment-specific overrides
- Integrate with Laravel’s configuration loading and service provider lifecycle
- Centralize maintainable configuration for modular applications
- Provide a consistent structure for runtime config access
Frequently asked questions about Composite Config
- What is Cartalyst Composite Config used for in Laravel?
- It is a PHP and Laravel package for building a composite configuration repository from multiple sources. It is useful when packages or modular applications need to merge defaults with overrides cleanly while keeping settings organized. The repository overview also describes overriding illuminate/config filesystem configuration with database-backed settings.
- How do I install cartalyst/composite-config with Composer?
- Install it as a Composer dependency using the package name cartalyst/composite-config. Because the provided release history only confirms a December 2020 tag, check the repository and Packagist metadata before choosing a version. Then run a dependency resolution pass and test against your target Laravel and PHP versions rather than updating blindly.
- Does cartalyst/composite-config support Laravel 10 or Laravel 11?
- The available evaluation does not confirm Laravel 10 or Laravel 11 support. Version 5.1.0 was published in December 2020, when Laravel 8 was contemporary and Laravel 6 LTS and 7 were still supported; Laravel 9 and later did not exist. Treat Laravel 10 and 11 compatibility as unverified until newer releases or CI coverage prove it.
- Which PHP versions does cartalyst/composite-config support?
- The v5.1.0 changelog adds PHP 8 support and was released in December 2020, which points to PHP 8.0 rather than later PHP 8 minors. The evaluation warns that PHP 8.1, 8.2, 8.3, and 8.4 deprecations and engine changes postdate the code and were not exercised. Confirm the widened Composer constraint admits your target PHP version.
- Is Cartalyst Composite Config still maintained?
- The key open question is whether v5.1.0 remains the latest release. If no newer 5.x or 6.x tag exists, the package has gone more than four years without a release as of the evaluation, which is a maintenance-rot signal. Check the repository tags and changelog before adopting it for new work.
- How is composite config different from Laravel's default config repository?
- Laravel's default illuminate/config repository primarily loads filesystem configuration files. Cartalyst Composite Config layers configuration from multiple sources into one composite repository so defaults and overrides can be combined. The package overview specifically frames this as overriding filesystem configuration with database-backed settings.
- Can I override database-stored settings with filesystem config in Laravel?
- The package description focuses on overriding illuminate/config filesystem configuration in a database, so the database side is the stated override source in the provided context. The overview also describes layering from multiple sources generally. Review the package documentation for the exact precedence rules between files and database values.
- Is cartalyst/composite-config safe for production on PHP 8.2 or PHP 8.3?
- There is no confirmed evidence that it was tested on PHP 8.2 or 8.3. The evaluation notes that deprecations such as dynamic properties in 8.2 and typed class constants in 8.3 postdate the December 2020 release. Production use on those versions should be treated as untested until you run a full regression suite and monitor deprecation logs.
- How should I test cartalyst/composite-config before a Laravel upgrade?
- Pin a known tag, perform a dependency-resolution pass, and run your full application regression suite against the target framework and PHP version. Check staging and production logs for deprecation notices because PHP 8-era deprecations may not fail requests. Also verify that illuminate and transitive constraints moved in lockstep.
- What alternatives exist to cartalyst/composite-config for database configuration in Laravel?
- The provided context does not name specific alternatives, so evaluate packages that explicitly support your Laravel and PHP versions and document their config precedence. You can also implement a custom config repository or service provider that merges file defaults with database overrides. Prefer options with recent releases and CI coverage for the PHP minors you deploy.
Weaver
How can I help you explore Laravel packages today?