Weave Code
Dynamically Configurable Mjr Bundle Laravel Package
modera/dynamically-configurable-mjr-bundle
A bundle for Laravel/PHP apps that lets you define and change configuration at runtime instead of hardcoding it, so settings can be adjusted dynamically without redeploying. Useful for flexible, per-environment or per-user behavior.
[READ-ONLY] Makes it possible to dynamically configure some aspects of MJR integration.
Frequently asked questions about Dynamically Configurable Mjr Bundle
- Is modera/dynamically-configurable-mjr-bundle a Laravel package?
- No. The Bundle suffix and Modera vendor namespace are Symfony conventions, and the package is built on Symfony's DI container, EventDispatcher, Config component, and Doctrine ORM. It has no Laravel service provider, facade, or Laravel contract, so it is not a drop-in dependency for a Laravel application. Treat it as a reference design rather than an installable Laravel package.
- Can I install this Symfony bundle in a Laravel app with Composer?
- Composer may resolve the package name, but installing it will not integrate it with Laravel. There is no service provider or Laravel extension point, and the bundle expects Symfony container, event, and config semantics. The realistic path is to copy the pattern into a Laravel-native settings layer, not to bridge the bundle.
- What is MJR in this package?
- The metadata does not define the MJR acronym, which makes domain relevance unclear. The description says it lets you dynamically configure some aspects of MJR integration using UIs, and it likely depends on a sibling Modera MJR core or backend bundle. Resolve what MJR means and whether the parent packages are usable before considering it.
- Which Laravel and PHP versions does this package support?
- It does not officially support Laravel at all. It is a 2016-era Symfony bundle with constraints around PHP 5.x to 7.0 and Symfony 2.8 or 3.x, so it will not run on a modern PHP runtime. The pinned dependency graph is likely to conflict with current Laravel and Symfony stacks.
- Is this package maintained and safe to use in production?
- No production maintenance signal exists. The last tagged release was June 2016, it has zero stars and zero dependents, and there is no visible security-response path. Any vulnerability in its transitive Symfony, Doctrine, or PHP dependencies would be yours to patch.
- Does it work with modern PHP 8 and Symfony 6?
- Almost certainly not. The bundle reflects 2016 runtime constraints and pinned dependencies that target PHP 5.x through 7.0 and Symfony 2.8 or 3.x. Upgrading it would be a rewrite, not a version bump.
- How do I install modera/dynamically-configurable-mjr-bundle?
- There is no supported Laravel installation path. In a legacy Symfony project you could try Composer require with matching PHP and Symfony versions, but expect dependency conflicts and missing sibling bundles. For Laravel, do not install it; extract the runtime-configuration pattern instead.
- What are the Laravel-native alternatives for runtime-configurable settings?
- Use spatie/laravel-settings with typed settings classes, or build a settings table with namespace, key, value, type, and encrypted flag columns. Load persisted settings in a service provider at boot and layer them above file and env config. Use Filament or Nova for the admin surface and Laravel encrypted casts for secrets.
- How should secrets and credentials be stored if I copy this pattern?
- Treat database-backed integration settings as sensitive. Use Laravel encrypted casts, write-only form fields, and masked display so credentials are never exposed in the UI. Add an audit trail and role-based access control rather than relying on whatever the parent backend provides. Do not assume the original 2016 bundle included encryption or governance.
- How do I handle config cache invalidation when settings change at runtime?
- Cache the resolved settings map and bust that cache plus Laravel's config cache in one transaction-aware step when an admin edit lands. Load persisted settings in a service provider at boot, layered above file and env config so UI values win while env remains the cold-start fallback. This is the hard part of the pattern and needs explicit testing.
Weaver
How can I help you explore Laravel packages today?