- How do I install filament-general-settings in a Laravel Filament project?
- Install the package with Composer, register the plugin on your Filament panel provider, publish and run the migrations, then define your settings schema. The plugin is designed for teams already using Filament, so typical setup effort is days rather than weeks. Confirm the supported Filament major against composer.json before scoping the work.
- Which Laravel and Filament versions does filament-general-settings support?
- The release notes do not state a support matrix, so confirm the required Laravel and Filament versions in the package's composer.json before committing. The RichEditor toolbarButtons documentation added in v1.0.27 may depend on the Filament version's RichEditor implementation. Test on your installed Filament major rather than assuming compatibility.
- Where does filament-general-settings store settings values?
- The available context does not confirm whether the package uses a dedicated table or an integration such as spatie/laravel-settings. Treat persistence as an unknown until you inspect the migrations and configuration. If you need secrets such as API keys or SMTP credentials, verify encryption support before moving them into the UI.
- Can I use filament-general-settings to manage logos, favicons, and social links?
- Yes, the package adds a Filament admin settings page for site identity and contact info including logos, favicons, site name, description, social links, email, phone, and address. It is intended to let operators edit these values without touching config files. Plan which values are content-scoped versus deployment-scoped before migrating them.
- Is filament-general-settings safe to use in production?
- The v1.0.27 release is a non-functional patch with documentation and a dev-only esbuild bump for a development-server CORS advisory, so there is no indicated production runtime exposure from that change. Production safety still depends on your Filament version, persistence choices, access control, and whether sensitive values are encrypted. Pin exact versions and review migrations before deploying.
- Does filament-general-settings support rich text settings with a custom toolbar?
- v1.0.27 adds documentation for the RichEditor custom field type, including the toolbarButtons configuration. That confirms rich-text values can be treated as a first-class setting type, useful for policy copy, footer text, or notification templates. Check that your Filament version supports the documented toolbarButtons behavior.
- How do I upgrade from v1.0.26 to v1.0.27 of filament-general-settings?
- v1.0.27 is a non-functional patch with documentation updates and a dev-only esbuild bump, with no API, schema, or config-contract changes. The risk relative to v1.0.26 is effectively nil and the upgrade is not time-critical. Still refresh your lockfile in CI to pick up the development dependency change.
- Does filament-general-settings have automated tests and a CI matrix?
- The assessment is based on release notes only and does not supply repository metadata, dependency manifests, or test-coverage data. Ask the maintainer whether the project has automated tests and a CI matrix you can use as a quality gate. Until confirmed, treat your own integration tests as the primary safety net.
- Who maintains filament-general-settings and what is the bus factor risk?
- The project is described as a single-maintainer effort by joaopaulolndev, which is a bus-factor consideration for production adoption. It is still on the 1.x line with a high patch cadence, which indicates active maintenance but argues for pinned exact versions. Plan a fork-or-vendor contingency and confirm the license permits it.
- How should I handle caching and multi-node deployments with filament-general-settings?
- The context does not state whether settings values are cached or what invalidates that cache across multiple nodes. If the package caches settings, confirm the invalidation strategy before running more than one app server. Otherwise, database-backed settings may behave differently per node until you add a shared cache or explicit refresh mechanism.