Weave Code
Config Bundle Laravel Package
gupalo/config-bundle
Symfony bundle for centralizing application configuration with typed settings, environment-specific overrides, validation, and cached container access. It simplifies managing flexible defaults and maintainable multi-environment deployments while keeping settings organized and consistent across servi...
Editable config rows backed by an EasyAdmin CRUD
Frequently asked questions about Config Bundle
- Is gupalo/config-bundle compatible with Laravel?
- No. It is a Symfony bundle built around Bundle classes, dependency injection extensions, and configuration trees, none of which Laravel auto-discovers. Composer may install it, but the bundle's services, validation, and compiler passes never load in a Laravel app.
- Can I install gupalo/config-bundle with Composer in a Laravel project?
- Composer may resolve it, but installing is not integrating. Laravel will not register the Symfony bundle, so its service definitions, config tree, and compiler passes stay inert. You would likely carry Symfony and Doctrine dependencies without getting the functionality.
- Why doesn't Laravel package auto-discovery find this bundle?
- Laravel auto-discovery looks for Laravel service providers listed in composer.json extra.laravel, while Symfony bundles register through Bundles.php and the Symfony Kernel lifecycle. This package exposes a Symfony Bundle subclass, not a Laravel ServiceProvider, so discovery has nothing to register. It is an ecosystem mismatch, not a configuration mistake.
- Does gupalo/config-bundle support typed and validated configuration values?
- The package overview describes typed, validated access to configuration values and layered defaults with environment-specific overrides. Those features are implemented through Symfony's configuration tree and service container, so they are available only inside a Symfony kernel. In Laravel you would need to rebuild that validation and resolution logic yourself.
- How does gupalo/config-bundle handle environment-specific overrides?
- It is designed to merge layered defaults with environment-specific overrides so settings stay consistent across services. The precedence and merge order are part of the bundle's Symfony configuration tree, and the assessment notes that the resolution semantics are not documented well enough to port confidently. Confirm the exact order between stored config, environment variables, and defaults before relying on it.
- Does gupalo/config-bundle work with Laravel's cache or config caching?
- No. Its cache integration is tied to Symfony's container and cache warmer or compiler pass lifecycle, not Laravel's config:cache or cache repository. Laravel's native config caching would not warm or invalidate this bundle's settings. A Laravel port would need new cache and invalidation hooks.
- Is gupalo/config-bundle actively maintained and safe for production?
- The assessment flags high supply-chain risk: zero stars, zero dependents, a single maintainer, and no external production usage from which to infer stability. There is no Laravel test matrix, so compatibility with your PHP and Laravel versions is unproven rather than merely untested. Treat it as code you own from day one and budget a spike before any production decision.
- What Laravel-native alternatives cover dynamic or layered configuration?
- Laravel's config() helper, env() layering, config/*.php files, and config:cache already cover most default-plus-environment override needs. For database-backed settings, a small Eloquent settings model with validation rules is usually enough. Evaluate those before porting a Symfony bundle.
- What would it take to port gupalo/config-bundle to Laravel?
- The assessment calls this a rewrite, not an adapter: the Bundle and DI extension become a service provider and bindings, the configuration tree becomes config files plus validation rules, and Doctrine entities become Eloquent models and migrations. Cache warmers and event subscribers need Laravel equivalents. The harder cost is reconstructing the original resolution semantics, which are not fully documented.
- Does gupalo/config-bundle conflict with Laravel's Symfony dependencies?
- It can. Symfony and Doctrine version constraints may pin Composer resolution and conflict with the symfony/* major versions Laravel already ships. That transitive dependency drag is a real upgrade risk even if the bundle never runs. Check the exact composer.json constraints before adding it to a Laravel project.
Weaver
How can I help you explore Laravel packages today?