Weave Code
Parameter Bundle Laravel Package
smartbooster/parameter-bundle
SmartBooster ParameterBundle offers a structured way to organize, access, and maintain application parameters in PHP projects. It simplifies configuration management across environments and provides a reusable parameter layer for consistent setup.
Provide an easy way to administrate your app parameters through each environment.
Frequently asked questions about Parameter Bundle
- Is smartbooster/parameter-bundle a Laravel package?
- No. The release notes describe a Symfony bundle with bundle configuration, a Doctrine parameter entity, and a Sonata Admin screen. The Laravel framing appears to be an intake error, so evaluate it as Symfony infrastructure rather than a Composer package built for Laravel.
- Can I use ParameterBundle in a Laravel application?
- Not directly. A Laravel host would need an adapter or a sidecar Symfony service, and neither is provided. For most Laravel teams, implementing a native Eloquent-backed settings provider using this bundle as a design reference is cheaper than running a second runtime.
- What dependencies does ParameterBundle require?
- It implies Doctrine ORM for entity persistence and Sonata Admin for the administration UI. The notes do not state whether Sonata is optional or a hard requirement, so treat it as required until confirmed. That is a large footprint for a key/value parameter store if you are not already running Doctrine and Sonata.
- How do I install and configure ParameterBundle in a Symfony application?
- The standard path is Composer require, register the bundle, configure it, run migrations for the parameter table, seed or load parameters, then inject the ParameterProvider into consumers. You also need to wire the ParameterLoadCommand and any Sonata admin configuration. The exact supported Symfony and PHP version matrix is not documented in the provided notes.
- How are parameter values typed and validated?
- The notes do not document value typing, so assume scalars or free-text unless you add your own schema and validation. There is no stated validation layer between the Sonata form and the stored entity. Define allowed keys, types, and constraints before exposing edits to non-developers.
- What is the precedence between database parameters, Symfony configuration, and environment variables?
- No precedence order is documented. You must decide explicitly whether ParameterProvider overrides services.yaml and .env values or only fills gaps. Ambiguity here is risky because a DB row silently overriding an environment variable can cause hard-to-trace behavior.
- How does caching work and when is it invalidated?
- Caching and invalidation are not described in the release notes. If you add a cache in front of the provider, invalidate it on Sonata admin save and on deploy. Without a defined strategy, edits may not take effect until the container or cache is rebuilt.
- What happens if the database is down or the load command has not run?
- This is not documented, but a Doctrine-backed provider will likely fail if it queries the database during container boot. Avoid using DB parameters in early bootstrap code, or implement a fallback to static config. Also define behavior for an empty parameter table rather than assuming the loader has run.
- Can parameters be scoped per environment, tenant, or channel?
- The bundle is described as managing parameters through each environment, but the notes do not document per-tenant or per-channel scoping. Treat storage as flat unless you add a scope column and filter in your provider. Multi-tenant use needs an explicit design for key namespacing and resolution order.
- Is ParameterBundle production-ready, and can I store secrets in it?
- Treat it as early-adopter code: v1.0.0, single-organization project, and no stated test coverage or CI signal. Do not store credentials or secrets in DB parameters, because the store is editable through Sonata and audit logging or role-based access is not documented. For production, add validation, change audit, backups, and access control before letting anyone edit parameters.
Weaver
How can I help you explore Laravel packages today?