- Can I use ongr/settings-bundle in a Laravel application?
- No. It is a Symfony bundle built around a Bundle subclass registered in the kernel, DI service definitions in XML/YAML, compiler passes, Symfony Form types, and Doctrine-style entity mappings. Laravel's ServiceProvider, type-hint container, config files, Eloquent, and Validator share no interfaces with any of these. There is no boot path for a Laravel app short of embedding a Symfony kernel.
- Does ongr/settings-bundle support Laravel 10 or Laravel 11?
- There is no Laravel support. The package has no Illuminate integration, no ServiceProvider, and no published compatibility with Laravel 10 or 11. Composer resolution is the first blocker: 2016-era constraints (PHP 5.5/7.x, Symfony 2.8/3.x) collide with illuminate/* on PHP 8.1+, and the v1.0.0 release notes say nothing about updated constraints.
- How do I install ongr/settings-bundle with Composer?
- In a Symfony project you would run composer require ongr/settings-bundle, register the bundle in the kernel, and configure it through Symfony configuration. In Laravel, installation is effectively not viable because the package expects Symfony bundle registration and DI wiring. Inspect composer.json first, since the PHP floor and Symfony version range decide whether resolution is even possible.
- What is ongr/settings-bundle used for?
- It provides a structured way to manage configurable application settings in Symfony: defining settings, persisting values through Doctrine, and reading them consistently from services, controllers, and templates. It adds cached access to reduce database overhead plus a simple retrieval API, keeping runtime configuration out of hardcoded logic. Its real value is the domain model: typed values, defaults overlay, a cache decorator, and a change event.
- Does ongr/settings-bundle work on PHP 8.1 and Symfony 6 or 7?
- Nothing in the v1.0.0 release notes mentions PHP 8.x support, Symfony 6/7 compatibility, updated Composer constraints, or Doctrine annotation-reader migration. Treat the original constraints as intact until composer.json is inspected. Known structural risks include PHP 8 deprecations, dynamic properties, typed-signature drift, and Doctrine annotation-reader changes.
- Is ongr/settings-bundle still maintained?
- The last release before v1.0.0 was 2016-10-04, roughly eight years earlier. A v1.0.0 tag after that dormancy is ambiguous—it can mean a returning maintainer or a single burst of tidying. "Stable to release major version" is a SemVer statement about API stability, not a support commitment, and with 7 stars and zero dependents there is no ecosystem validation.
- What are Laravel alternatives to ongr/settings-bundle for runtime-editable settings?
- For deploy-time configuration, Laravel's own config/*.php files are the right tool. For runtime-editable, admin-managed settings, use a package such as spatie/laravel-settings or a small Eloquent-backed settings table with validation, a cache decorator, and events. Porting the ONGR domain model—typed values, defaults overlay, scoped resolution, and change events—is more practical than adopting the Symfony code.
- What events were added in ongr/settings-bundle v1.0.0, and can Laravel use them?
- v1.0.0 adds events, most plausibly domain events fired on setting write (before or after change) carrying scope, key, old value, and new value. They are dispatched on the Symfony event dispatcher, so Laravel's dispatcher cannot consume them without a bridge. The payload shape is the useful part—it is exactly the hook a cache-invalidation and audit design needs, and you can replicate the same contract natively in a Laravel port.
- Does ongr/settings-bundle support scoped or hierarchical settings like global, tenant, and user?
- Scope resolution and default merging are the package's main sources of value, alongside typed values and a cache decorator. Whether you need a global-to-tenant-to-user hierarchy or flat key/value config determines how much of the design is worth replicating. Verify the actual scope API in the source before relying on it.
- Is ongr/settings-bundle safe for production, or should I fork and port it?
- Risk is high: long dormancy, no stated PHP 8 or Symfony 6/7 support, no dependents, and unresolved dependency constraints. The MIT license means forking is legally unencumbered, but the Symfony-specific parts would need rewriting as a ServiceProvider, config file, Eloquent models, and Validator rules. Unless your organisation has a legitimate Symfony footprint, port the domain model into Laravel rather than adopting the bundle.