- What is quadrubo/filament-model-settings used for?
- It is a Filament plugin for managing settings that are specific to individual models in a Laravel admin panel. It adds a settings page and a reusable form component so you can store, edit, and read model-specific configuration values from Filament. It fits best in back-office/admin tiers where Filament is already the standard UI.
- How do I install quadrubo/filament-model-settings in a Laravel app?
- Install it with Composer using quadrubo/filament-model-settings, then register the plugin on the relevant Filament PanelProvider. You will also need to publish or author the settings classes and run any required migrations as described by the package. Treat this as a short integration spike and verify it in a non-production panel first.
- Does this package require Filament, or can I use it with plain Laravel?
- The package is described as a Filament plugin that adds a settings page and reusable form component, so it is intended for applications that already use Filament for administration. In a Livewire/TALL or Filament shop the marginal cost is low, but in an Inertia, API-first, or Blade-only application it introduces an entire UI framework for one settings screen. If you do not use Filament, a plain config file or a single settings class is likely cheaper.
- Which Laravel, PHP, and Filament versions are supported?
- The provided technical assessment targets Laravel 10/11/12, PHP 8.2+, and a Filament v3+ panel already in production, but you should confirm the exact Composer constraints declared by version 2.0.1. Check whether the Filament constraint is a caret range or a ceiling before adopting it. Pin the package exactly and lock the Filament major alongside it so a Composer update cannot silently move the host framework underneath the plugin.
- How do I store and read per-model settings with this package?
- The package layers Filament-native settings management over a settings store, adding a settings page and reusable form component for model-specific configuration values. The exact storage backend and whether it reuses an existing settings table or creates its own should be confirmed in the package docs and source. Define one settings class for a low-risk model first, then verify how values are read through the simple API.
- Can I control who can access the Filament settings page?
- Authorization is important because settings records often hold feature flags, integration keys, or per-tenant configuration. The provided overview does not establish whether access is policy-driven per model or controlled by a single gate on the panel page, so verify that before exposing the surface. Add explicit access controls so non-admins cannot reach the settings page in production.
- Is it suitable for global app settings or only per-model settings?
- The package is specifically for model-specific settings, so it is strongest when at least one model has genuinely per-record configuration such as tenant branding, notification preferences, feature toggles, or per-account limits. If the settings are global rather than per-model, a plain config file or a single spatie/laravel-settings class is cheaper and this package is overkill. Choose it when the Filament UI and per-model workflow justify the dependency.
- What changed between v2.0.0 and v2.0.1, and should I upgrade?
- The v2.0.1 patch has no disclosed behavioural change in the provided context, so the safe assumption is that it is a defect fix but not a confirmed one. Request the commit range from the maintainer or diff it yourself before pinning. Adopters already on v2.0.0 should generally take patch releases in young majors, but read the diff first given the missing notes.
- How should I test model settings before deploying to production?
- Install the package, register the plugin, and define one settings class for a low-risk model in a non-production Filament panel. Run migrations against a restored production snapshot where applicable and diff the settings rows before and after. Also test authorization with non-admin users, and confirm how settings are cached and what invalidates them across application servers.
- What alternatives exist if I do not use Filament?
- If the settings are global, use a plain Laravel config file or a single spatie/laravel-settings class instead of introducing Filament. If you need a back-office UI but do not use Filament, you would be adding an entire UI framework dependency for one settings screen, which is usually a poor trade. Consider this package only when Filament is already your standard admin layer and the settings are genuinely per-model.