- Can I use lexxpavlov/settingsbundle in a Laravel application?
- Not idiomatically. It is a Symfony bundle, and Laravel's service container cannot load a Symfony Bundle subclass or read its Extension::load() wiring. You could port the settings service and repository pattern to Eloquent, but composer require alone will not give you a working Laravel package.
- Does lexxpavlov/settingsbundle support Laravel 10, 11, or 12?
- There is no Laravel version support signal. The package is built around Symfony bundle conventions and Doctrine-oriented persistence, and the last release was 2021-03-25, so there is no evidence of Laravel 10, 11, or 12 compatibility. Treat it as a Symfony package, not a Laravel dependency.
- What is lexxpavlov/settingsbundle used for?
- It provides database-backed application settings management for Symfony projects. You define, store, and retrieve configuration values through a service API instead of editing configuration files, with default-value fallback for missing entries. It is lightweight and intended to fit into existing Symfony and Doctrine projects.
- How do I install lexxpavlov/settingsbundle?
- Installation is via Composer, but the package is a Symfony bundle, so you also need Symfony bundle registration and configuration. In a Laravel app there is no equivalent bundle registration step, which is why installation alone does not make it usable. Check the package's composer.json PHP and doctrine/orm constraints before trying it under PHP 8.2 or newer.
- Is lexxpavlov/settingsbundle maintained?
- Maintenance risk is high. The last release was 2021-03-25, the project has a single maintainer, about 10 stars, and 0 dependents. There is no community triage or recent compatibility signal for modern PHP or framework versions.
- What are Laravel alternatives to lexxpavlov/settingsbundle?
- Use a Laravel-native settings package instead of porting a Symfony bundle. Mature options such as spatie/laravel-settings solve the same database-backed key/value settings problem with Eloquent, Laravel service provider integration, and active maintenance. That avoids adding a second ORM or owning a fork of a low-usage library.
- Can I port lexxpavlov/settingsbundle to Laravel?
- Yes, but port the pattern rather than the package. Extract the settings service and repository, discard the Symfony bundle plumbing, and reimplement persistence against Eloquent. The API surface is small, so this is typically days of work, but you then own a fork of a 10-star, single-maintainer library.
- Does lexxpavlov/settingsbundle work with PHP 8.2 or PHP 8.3?
- That is not confirmed by the available context. The assessment flags no PHP 8.1, 8.2, or 8.3 compatibility signal, so you should inspect composer.json constraints and run a clean composer install against your current stack. If that install fails, stop evaluating the package for that project.
- Is lexxpavlov/settingsbundle safe for storing secrets or sensitive settings?
- Be cautious. The technical assessment flags no typed values, encryption, or audit trail, and settings stores are a common place for secrets and PII to leak. If you borrow the pattern, add encryption, access control, and an audit trail before storing sensitive values.
- How should I test a Laravel port of lexxpavlov/settingsbundle?
- Test the ported service rather than the original bundle. Write feature tests around get, set, default fallback, and Eloquent persistence, and add coverage for cache interactions and permission boundaries. If you keep the original Symfony package, test it only within a Symfony and Doctrine test setup, not inside a Laravel test suite.