Weave Code
Laravel Site Settings Laravel Package
visual-ideas/laravel-site-settings
A Laravel package for managing site settings in the database. Define settings, read typed values anywhere in your app, and cache them for fast access, so editable options like site name, contact details, or feature flags stay out of config files and code.
Easy laravel cached settings (stored in MYSQL) package with MoonShine/Filament Laravel Admin GUI
Frequently asked questions about Laravel Site Settings
- How do I install visual-ideas/laravel-site-settings in a Laravel app?
- Install it with Composer using composer require visual-ideas/laravel-site-settings, then follow the repository README to publish its config and migrations. Run the migrations against MySQL before reading or writing settings. If you plan to use the admin UI, verify the MoonShine or Filament adapter against the exact version installed in your app.
- Does this package support the current Laravel version?
- The provided assessment does not confirm support for the current major Laravel release. The last release date shown is 2024-02-26, so Laravel and PHP version drift is a real compatibility risk. Pin the package version and validate Composer constraints against your Laravel, PHP, MySQL, Filament, and MoonShine versions before adopting it.
- How does caching work for Laravel site settings and is cache invalidation safe across multiple servers?
- The package is described as a cached settings store backed by MySQL, so reads are intended to avoid hitting the database on every request. However, the assessment flags cache invalidation correctness across multiple app nodes and queue workers as a key risk rather than confirming it is solved. Test read, write, and invalidation behavior against your production cache backend before relying on it for critical settings.
- Are settings typed, validated, encrypted, or audited?
- The package advertises typed setting values, but the assessment does not confirm built-in validation, encryption, or audit logging. It also warns that database-backed sensitive configuration can have weaker review and audit controls than code-based config. Avoid storing secrets unless you verify encryption and access controls, and add application-level validation where needed.
- Can I use this package in a multi-tenant Laravel application?
- The assessment says the package is less attractive for multi-tenant environments because it is MySQL-specific and tenant scoping is not confirmed. You would need to add tenant isolation and verify cache keys do not leak settings between tenants. Treat it as an accelerant for simple settings, not as a multi-tenant platform primitive.
- What are alternatives to visual-ideas/laravel-site-settings for Laravel settings?
- You can build an internal settings repository backed by MySQL and cache, or evaluate other Laravel settings packages on Packagist. Compare release dates, Laravel version support, cache invalidation behavior, admin panel compatibility, and maintenance activity. The assessment recommends wrapping any package behind a thin internal SettingsRepository interface so it can be replaced without touching product code.
- Is visual-ideas/laravel-site-settings actively maintained?
- The provided assessment indicates limited community validation and uncertain ongoing maintenance, citing a low star count, a package score of 0.23, and a last release date of 2024-02-26. It also flags single-maintainer bus factor as a risk. Check the repository issues and commit activity, and keep a documented fork or replacement plan before relying on it for critical runtime settings.
- Does it work with MoonShine and Filament admin panels?
- The package includes MoonShine and Filament Laravel Admin GUI adapters, so it can provide an admin interface for editing settings. The GUI value is limited if your application does not already standardize on one of those panels. Validate the adapter against the exact Filament or MoonShine version in use, and treat admin-panel major upgrades as a re-validation event.
- How should I handle defaults and fallbacks if the database or cache is unavailable?
- The assessment lists fallback behavior when the database or cache is unavailable as a key question, so do not assume it is handled automatically. Keep config-based fallbacks for critical settings and seed defaults from existing config files during migration. Test database and cache failure modes in staging before enabling the package for production administration.
- What is a safe production rollout plan for this Laravel settings package?
- Start with a time-boxed proof of concept covering read, write, cache invalidation, default fallback, and admin authorization. Pin the package version, review migrations and config, and introduce a thin internal SettingsRepository interface with seeded defaults. Roll out behind a feature flag to a low-risk environment, monitor multi-node cache behavior, and document an exit plan before using it for critical runtime settings.
Weaver
How can I help you explore Laravel packages today?