- Can I install smirik/config-bundle in a Laravel application?
- No. smirik/config-bundle is a Symfony bundle (Smirik\ConfigBundle), not a Laravel package, and it has no service provider, facade, or package auto-discovery. Composer requiring it into a Laravel app will not wire it up, and you would have to port its merge and caching logic yourself.
- Does smirik/config-bundle support Laravel 9, 10, or 11?
- No. It follows Symfony conventions and likely pins older symfony/* and PHP constraints typical of its vintage. Laravel 9+ requires PHP 8.0+ and modern Symfony components, which can produce Composer solver conflicts or an untested force-install. There is no Laravel version support for this bundle.
- What does smirik/config-bundle actually do?
- It stores key/value application configuration rows in a Doctrine-backed database table. It type-casts values, layers defaults against environment-specific overrides, exposes a service for reading and writing config, adds a Twig helper, and caches reads. The purpose is changing runtime options without code deployments.
- How do I install smirik/config-bundle?
- In a Symfony application you would require it with Composer, register Smirik\ConfigBundle in your kernel or bundles.php, and configure Doctrine plus the bundle's YAML/XML service definitions. There is no Laravel installation path. Verify the composer.json constraints and license before attempting anything.
- Is smirik/config-bundle still maintained?
- There is no maintenance signal in the assessment: no stars, no dependents, no release cadence, no issue activity, and no security disclosure path. That means no external validation and no CVE remediation. Treat it as dormant unless you can confirm recent commits and tagged releases.
- What is the Laravel equivalent of smirik/config-bundle?
- Laravel already provides config/*.php, env(), the config repository, and config:cache for cached configuration. For database-backed settings, use a maintained package such as spatie/laravel-settings or a small custom Eloquent model plus Cache::remember. Both avoid a foreign bundle translation layer.
- How do I store application settings in the database in Laravel?
- Create a settings table with key, value, and type columns, back it with an Eloquent model, and read through a service that caches values with Cache::remember. Validate and cast on write, then invalidate the cache on save. Merge defaults and environment overrides in a service provider or a dedicated repository class.
- What are the PHP and Symfony version constraints for smirik/config-bundle?
- The assessment flags this as unverified, but bundles of this vintage typically pin symfony/* to 2.x or 3.x and PHP to 5.x-7.x. Those constraints conflict with Laravel 9+ and modern PHP 8.x. Inspect the composer.json require blocks before any install attempt.
- Does smirik/config-bundle have tests or security support?
- There is no automated test suite signal in the assessment, and no security disclosure path. Without tests running on a supported PHP version, correctness and edge-case behaviour are unknown. That is a high technical risk for a production dependency.
- Should I use smirik/config-bundle as a dependency or a design reference?
- Use it as a design reference only. Its pattern of Doctrine-backed key/value settings, type casting, defaults with overrides, service access, Twig helper, and caching is reproducible natively in Laravel within a few days. Adopting the bundle adds a translation layer and permanent cognitive overhead with no offsetting capability.