Weave Code
Filament System Settings Laravel Package
rectitude-open/filament-system-settings
Filament System Settings adds a settings management page to your Filament admin panel, letting you define and edit application settings stored in the database. Configure fields, groups, and values from one place, then read them anywhere in your Laravel app.
At a glance
Frequently asked questions about Filament System Settings
- How do I install rectitude-open/filament-system-settings in a Laravel app?
- Install it with Composer using composer require rectitude-open/filament-system-settings, then follow the README to publish and run the package migrations. Register the plugin in your Filament panel provider so the settings page appears in the admin panel. After that, define your settings fields and groups and start editing values from the Filament UI.
- Which Laravel, PHP, and Filament versions does v1.3.0 support?
- Check the composer.json constraints for v1.3.0 before upgrading, since Laravel, PHP, and Filament support can change between releases. The package is built for Laravel applications that already use Filament admin panels. Confirm your installed Filament major version matches the constraint, and test in staging if you are on the edge of the supported range.
- What changed with the site_url field in version 1.3.0?
- Version 1.3.0 removes the site URL field from the settings form, although the release notes describe this as a feature. If your application reads, displays, validates, or migrates that setting, the change can behave like a breaking change. Audit your code and templates for references before you upgrade.
- Is removing the site_url field a breaking change for my application?
- It can be. Removing a setting field is only harmless if no code, admin workflow, email template, redirect, or SEO metadata depends on it. Treat it as breaking for internal consumers unless you have verified that nothing reads the stored value or expects the form field to exist. Pin the previous version until you have completed that audit if site_url is business-critical.
- Does upgrading to v1.3.0 delete existing site_url values from the database?
- The available release information does not clearly state whether the upgrade deletes persisted values, stops rendering the field, or both. Back up your settings data and inspect the migration and package code before running the upgrade in production. If stale values remain, you can leave them inert until you confirm they are safe to remove with a cleanup migration.
- What should I use instead of the removed site_url setting?
- For most Laravel applications, config('app.url') and the APP_URL environment variable should be the canonical source of truth for the site URL. Update links, emails, redirects, SEO metadata, and tenant configuration to read from configuration instead of the settings table. Publish internal guidance that the site URL is no longer managed in Filament system settings.
- Can I store secrets or environment-controlled values in Filament System Settings?
- No. This package is for editable operational settings stored in the database, not for API keys, passwords, or values that must remain environment-controlled. Keep secrets in environment variables or a dedicated secrets manager. Use system settings for values that administrators genuinely need to change at runtime.
- How do I read settings values in my Laravel code and should I cache them?
- Use the helper or settings model documented in the package README to read values anywhere in your Laravel application. Because settings are stored in the database, cache them where appropriate so you are not querying the settings table on every request. Clear your config and settings caches after deployments or upgrades.
- How should I test the v1.3.0 upgrade before deploying to production?
- First inventory every reference to site_url across code, config, database settings, email templates, frontend views, and API responses. Back up production-like settings data, upgrade in staging, and verify the admin settings page, cached config, policies, and runtime URL behavior. Then deploy the package update and any data cleanup together.
- What are alternatives to Filament System Settings for Laravel?
- Alternatives include spatie/laravel-settings with a custom Filament page, other Filament settings plugins, or a small custom settings page built directly in your panel. Choose based on whether you need typed settings classes, per-team settings, or simple database-backed key-value fields. Filament System Settings is a good fit when you want a lightweight admin-managed settings page without extra domain complexity.
Weaver
How can I help you explore Laravel packages today?