- How do I install ferdiunal/nova-settings in a Laravel Nova application?
- Install it with Composer using composer require ferdiunal/nova-settings, then follow the package README to publish any config or migrations and run php artisan migrate. You should already have Laravel Nova and Spatie's laravel-settings installed because nova-settings builds on them. After installation, register the settings classes you want to expose in the Nova panel.
- Which Laravel and Laravel Nova versions are supported by nova-settings?
- The package is designed for Laravel applications that use Laravel Nova and Spatie laravel-settings. Exact Laravel and Nova version constraints are defined in the package composer.json, so check those before installing. Because Nova major versions have different APIs, match the package branch or version to your Nova version.
- How do I define settings groups and field types for the Nova Settings UI?
- Define Spatie-style settings classes with typed properties and group them using the package configuration. Each group becomes a section in the Nova Settings interface, and property types determine the form inputs. Keep related settings in the same group so admins can find them easily.
- Does nova-settings cache setting values, and how is the cache refreshed?
- Yes, the package advertises cached setting values for fast access. Values are loaded through Spatie settings and the package cache layer, so changes made in Nova should be reflected after the package refreshes or you clear the cache. If you see stale values in production, clear Laravel's cache and any package-specific cache.
- How do I read a setting value anywhere in Laravel using the helper?
- Use the package simple helper to retrieve settings in controllers, services, or Blade views without calling Spatie classes directly. The helper resolves the registered setting and returns its typed value. Check the README for the exact helper name and key or group syntax for your version.
- Can non-technical admins edit application settings from Laravel Nova?
- Yes, the main purpose is to let authorized Nova users manage settings through forms instead of editing code or config files. Changes are saved through Spatie settings storage and can be read by the helper across the app. You still control which users can see and edit settings through Nova permissions.
- How do I restrict access to the Nova Settings panel?
- Use Nova authorization features, such as gates and policies, plus any access configuration provided by nova-settings to limit the panel to trusted administrators. In production, avoid granting settings access to all Nova users by default. Test the permissions with a non-admin Nova account before deployment.
- What is the deployment process for nova-settings in production?
- Deploy the package like any Laravel and Nova dependency: install via Composer, run migrations, and clear or rebuild caches as part of your release process. Settings edited in Nova are stored in the database, so database backups and migrations matter. After deploying changes to setting definitions, clear caches so the helper reads the latest values.
- How does nova-settings compare with using Spatie laravel-settings by itself?
- Spatie laravel-settings provides the backend settings classes, storage, and typed values, but no Nova admin UI. Nova Settings adds a Nova interface, grouped editable fields, caching convenience, and helper access for application code. Choose Spatie alone for code-managed settings, or nova-settings when admins need to edit values safely.
- Is ferdiunal/nova-settings actively maintained, and what should I check before adopting it?
- Check the GitHub repository and Packagist release history for recent commits, Laravel and Nova compatibility updates, and open issues before adopting it. Because it depends on Spatie laravel-settings and Nova, confirm the package version you choose supports your major versions. For long-term projects, pin a tested version and review alternatives if maintenance slows.