Weave Code
Nova Settings Laravel Package
kraenkvisuell/nova-settings
A Laravel Nova package for managing application settings directly from the Nova admin panel. It provides a settings interface for editing and storing configuration values, so teams can update settings without code changes or redeploys.
A Laravel Nova tool for editing custom settings using native Nova fields.
Frequently asked questions about Nova Settings
- What is kraenkvisuell/nova-settings used for?
- It is a Laravel Nova tool for managing application settings inside the Nova admin panel. It gives teams a settings interface for editing and storing configuration values without code changes or redeploys. It uses native Nova fields, so the editing experience matches other Nova forms.
- How do I install kraenkvisuell/nova-settings?
- Install it with Composer using composer require kraenkvisuell/nova-settings. Then register the tool in the tools() method of app/Providers/NovaServiceProvider.php. Follow the repository README for any required publish, migration, or configuration commands.
- Which Laravel and Nova versions does kraenkvisuell/nova-settings support?
- Compatibility is defined by the package's composer.json constraints, so check the GitHub repository or Packagist listing for the supported Laravel and Nova versions. This matters most when you are running Nova 4 or Nova 5, because tool APIs and dependencies can differ. Confirm the constraints before adding it to an existing application.
- Does nova-settings use native Nova fields?
- Yes, the package is described as editing custom settings using native Nova fields. That means you can build settings forms with familiar field types rather than a separate custom UI. The exact field configuration is documented in the README.
- How do I define which settings appear in the Nova tool?
- Settings and fields are defined according to the package's configuration approach, which the README covers. You typically declare the settings you want to manage and attach native Nova fields to them. Review the repository examples before adding custom fields to production.
- Where does nova-settings store the settings values?
- The package provides a settings interface for editing and storing configuration values from Nova. The repository README is the authoritative source for the storage mechanism and any publish or migration steps. Plan how your application will read those stored values at runtime.
- Can I control who can access or edit settings in Nova?
- Use Nova's authorization mechanisms, such as policies or Gates, and any menu visibility options the tool exposes to restrict access. Settings often contain sensitive configuration, so limit editing to trusted administrators. Check the README for package-specific authorization guidance.
- Is kraenkvisuell/nova-settings suitable for production use?
- It can be used in production if it matches your Laravel and Nova versions and your authorization and storage requirements are covered. Test the tool in staging first, especially if settings affect caching, queues, or third-party services. Review the repository's maintenance activity and open issues before relying on it.
- How do I test settings changes made with nova-settings?
- Test changes in a non-production environment and verify that the values are saved and read correctly by your application. If your app caches configuration, clear or refresh the relevant caches after updates. Add automated tests around the code paths that consume the settings.
- What are alternatives to kraenkvisuell/nova-settings?
- Alternatives include Spatie's laravel-settings package, custom Nova resources, or plain Laravel configuration files managed through deployment. The main advantage of nova-settings is editing values with native Nova fields from the admin panel. Choose based on your need for runtime editing, auditability, and Nova integration.
Weaver
How can I help you explore Laravel packages today?