Weave Code
Settings Bundle Laravel Package
phpmob/settings-bundle
phpmob/settings-bundle is a Symfony bundle for centralized application settings, letting you define, persist, and retrieve configuration values through a clean, reusable API. It’s a practical fit for projects that need editable settings beyond static config files.
phpmob/settings-bundle is a Symfony bundle that provides persistent, database-backed application settings using Doctrine ORM. It lets you store and retrieve configuration values—such as site options, feature flags, or user preferences—through a simple API, keeping them editable at runtime without touching config files.
Settings are exposed via a manager service and integrate cleanly with Symfony's dependency injection and Doctrine entity management. Values are typed and can be read individually or loaded in bulk.
- Doctrine ORM storage for editable, persistent settings
- Simple get/set API through a Symfony service
- Support for scalar and array value types
- Seamless Symfony bundle and DI integration
- Runtime-editable configuration without file changes
Frequently asked questions about Settings Bundle
- Is phpmob/settings-bundle a Laravel package?
- No. phpmob/settings-bundle is a Symfony setting bundle that integrates with Symfony's service container and supports database-backed settings for dynamic configuration. It is not documented as a Laravel package and does not appear to ship a Laravel service provider or facade. Laravel applications can consume Symfony components, but this package is designed around Symfony bundle conventions.
- How do I install phpmob/settings-bundle?
- Install it with Composer using the package name phpmob/settings-bundle, then register the bundle in your Symfony application's kernel as you would any Symfony bundle. In a Laravel application there is no documented package auto-discovery or service provider, so you would need custom integration work. Always verify the package's Composer constraints against your current PHP, Laravel, and Symfony component versions before installing.
- Does phpmob/settings-bundle support Laravel 10 or Laravel 11?
- There is no published Laravel support matrix in the provided context. Release 1.2.2 adds SF4 support, which most likely means Symfony 4 component compatibility, and Symfony 4 is end-of-life. Treat this as legacy-stack compatibility rather than evidence of support for modern Laravel versions. Test dependency resolution and runtime behavior in a staging branch before relying on it in Laravel 10 or 11.
- What does SF4 Support in version 1.2.2 mean?
- The release note is a one-line statement, so it is unclear whether SF4 means Symfony 4 components, the full Symfony 4 framework, or another target. It likely indicates Symfony 4 component compatibility, which matters because Laravel depends heavily on Symfony components. Confirm by inspecting the package's composer.json constraints and changelog before assuming a specific compatibility level.
- Can I use phpmob/settings-bundle with Laravel's service container?
- The package is built around Symfony's service container, while Laravel uses its own container with similar but not identical behavior. There is no documented Laravel integration, so you would likely need custom wiring or a service provider. Evaluate whether the bundle's container, event dispatcher, and configuration assumptions can be adapted cleanly to Laravel before committing.
- How are settings stored and retrieved with phpmob/settings-bundle?
- The package provides a flexible settings management layer for defining, storing, retrieving, and editing configuration values. It supports database-backed settings for dynamic application configuration, which lets you change values without editing static configuration files. The exact schema and API are not covered in the provided excerpt, so review the repository README and source for storage details.
- Is phpmob/settings-bundle safe to use in production?
- Technical risk is moderate until the compatibility matrix is verified. A patch release that expands platform support can still introduce transitive dependency conflicts, autoloading changes, or subtle container differences. Pin the version, run unit, integration, and smoke tests in a staging environment, and keep a rollback plan to the prior package version and lockfile.
- What Laravel and Symfony versions does phpmob/settings-bundle support?
- The provided context does not include an official support matrix. Version 1.2.2 adds SF4 support, but it is unclear whether Symfony 3.x constraints are retained or whether this is a hard migration to Symfony 4. Inspect composer.json and run composer why symfony/* and composer why illuminate/* to verify what your application can resolve.
- What are alternatives to phpmob/settings-bundle for Laravel applications?
- For Laravel-native settings management, evaluate packages designed specifically for Laravel's container, configuration, and database layers rather than a Symfony bundle. A custom database-backed settings table with caching is also a common alternative for simple use cases. Compare maintenance activity, documented Laravel version support, and test coverage before choosing.
- How should I test upgrading to phpmob/settings-bundle 1.2.2 in a Laravel app?
- Create a branch and update only this package first, then inspect composer why symfony/* and composer why illuminate/* to understand the resolved dependency graph. Run your unit, integration, and smoke tests, and avoid combining the update with unrelated framework upgrades unless Composer forces it. Canary the change in a non-production environment and keep a rollback path to the previous package version and lockfile.
Weaver
How can I help you explore Laravel packages today?