Weave Code
Config Laravel Package
orchestra/config
Orchestra Config provides a Laravel-friendly configuration component for Orchestra Platform, helping packages and extensions register, merge, and manage config files through a consistent API. It integrates cleanly with Laravel’s configuration system.
Configuration Component for Laravel and Orchestra Platform
Frequently asked questions about Config
- What is orchestra/config used for in Laravel?
- Orchestra Config is a configuration component for Laravel and Orchestra Platform that helps packages and extensions register, merge, and manage config files through a consistent API. It integrates with Laravel's configuration system, so values remain accessible through the config() helper and the standard config repository. It is typically used by packages that ship publishable defaults while letting the host application override them. Note that v6.0.0 targets Laravel 8 and has no known third-party dependents.
- Which Laravel versions does orchestra/config support?
- The latest major, v6.0.0, exists solely to add Laravel 8 support and is coupled to that framework line. Laravel 9 and later are not installable because Composer resolution fails on the illuminate/* constraint. On Laravel 6 or 7, moving to v6.0.0 forces a framework upgrade first. The last viable option for older applications is to pin the appropriate 5.x tag.
- Does orchestra/config work with Laravel 9 or Laravel 10?
- No. On Laravel 9 and later, Composer resolution fails and no application-side work fixes it. Your options reduce to pinning the last viable v5.x tag or forking the constraint yourself. There is no published indication of an open branch or PR adding Laravel 9+ support.
- How do I install orchestra/config in a Laravel 8 application?
- Run composer require orchestra/config and let Laravel's package auto-discovery register the service provider. Publish the package config with vendor:publish, then diff the published file against any existing application copy rather than overwriting it. Plan for roughly half a day including regression testing, because config changes load at boot. Confirm your application is on Laravel 8 before attempting the install.
- Is orchestra/config actively maintained?
- The maintenance signal is weak. Shipping framework support as the headline of a major release suggests slow tracking rather than active development, and there are zero dependents exercising the code in production. It is a single-maintainer package one framework generation behind, which is a credible abandonment profile. There is no stated CI matrix across PHP and Laravel versions, so confidence is bounded by what you verify yourself.
- How do I upgrade orchestra/config from v5.x to v6.0.0?
- First confirm your application runs Laravel 8, since v6.0.0 is coupled to that major and will not install elsewhere. Diff composer.json between the tags to see whether the illuminate/* constraint was raised, widened, or narrowed. Publish the new config to a scratch path and diff it against your application's published copy, reconciling keys by hand rather than overwriting. The one-line changelog does not distinguish a constraint bump from renamed config keys, so assume breaking until diffed.
- What changed in orchestra/config v6.0.0?
- Publicly, the release is presented as adding Laravel 8 support, with a one-line changelog and no visible upgrade guide. We cannot tell from the changelog whether the change is constraint-bump-only or also includes renamed config keys, namespaces, or facades. Treat it as breaking until you have diffed composer.json and the published config between v5.x and v6.0.0. Check the repository for an UPGRADING.md or fuller release notes.
- What is the blast radius of adding orchestra/config to an application?
- Configuration is a cross-cutting concern loaded at boot, so the integration surface is narrow but the blast radius is wide. A defect in a config-layer package surfaces application-wide rather than inside the one feature that adopted it. Budget regression testing accordingly and do not treat it as only config work. This risk is medium-high for most applications.
- Should I use orchestra/config in a new Laravel project?
- For a new project on Laravel 9 or later, no, because it is not installable. For a maintained Laravel 8 application that already uses Orchestra Platform conventions, it can slot into existing provider registration and vendor:publish workflows. For anything else, evaluate alternatives that track current Laravel releases. This is a dependency-governance decision, not a feature decision.
- What are the alternatives to orchestra/config for package configuration in Laravel?
- Most Laravel packages do not need a wrapper at all; a service provider using mergeConfigFrom plus a publishable config file covers the standard use case. spatie/laravel-package-tools and the framework's own config repository are common starting points for package scaffolding. If you need Orchestra Platform compatibility specifically, pin a known-good tag and fork the constraint for newer Laravel majors. Compare maintenance cadence and CI coverage before adopting any alternative.
Weaver
How can I help you explore Laravel packages today?