Weave Code
Nova Settings Laravel Package
epigra/nova-settings
Epigra Nova Settings adds a settings management tool to Laravel Nova, letting you create, organize, and edit application settings from a dedicated interface. Store key/value settings in the database and access them easily throughout your Laravel app.
A Laravel Nova tool for editing custom settings using native Nova fields.
Frequently asked questions about Nova Settings
- How do I install epigra/nova-settings in a Laravel Nova application?
- Install the package with Composer using composer require epigra/nova-settings, then register the tool in your Nova service provider and publish or run the package migrations as described in the README. Verify any asset publishing and configuration steps against your exact Nova version. Run the installation in a non-production environment first because the package has limited community validation.
- Which Laravel, PHP, and Nova versions are supported by epigra/nova-settings?
- The provided repository context does not list a confirmed compatibility matrix for Laravel, PHP, or Nova. Check the package composer.json and README for version constraints, then test against your exact Nova major version and PHP runtime. Because Nova is commercial and changes across releases, pin the package version and record the Laravel, Nova, and PHP matrix you validated.
- How do I configure epigra/nova-settings after installation?
- Configuration typically involves registering the Nova tool, publishing the package config and migrations if provided, and defining the settings fields your admins should edit. Confirm the exact publish tags and config keys in the README before wiring it into your app. Keep environment-level configuration and secrets outside the package.
- How are settings stored and accessed with epigra/nova-settings?
- The package stores key/value settings in the database and lets you access them from your Laravel application. You define settings fields in the Nova tool interface and edit their values through native Nova fields. The exact retrieval API, caching behavior, and data model should be verified in the source or README before relying on them in production.
- Can I edit settings with native Nova fields using epigra/nova-settings?
- Yes. The package is designed to let you create, organize, and edit application settings using native Nova fields, so administrators work inside the familiar Nova interface. You still need to define the settings schema and confirm that the specific Nova field types you need are supported.
- Is epigra/nova-settings suitable for API keys, passwords, or secrets?
- Do not treat this package as a secret store. The overview describes database-backed key/value settings and does not establish encryption, hardened access controls, or audit guarantees for sensitive values. Keep credentials and infrastructure secrets in environment variables or a dedicated secret manager.
- Does epigra/nova-settings support validation, permissions, caching, audit logs, or multi-tenancy?
- The provided overview does not confirm built-in validation, role-based permissions, caching, audit history, or tenant-scoped settings. Treat those as requirements to verify in the source and test explicitly before depending on them. If you need audit trails, tenant authorization, or controlled caching, plan to add them or choose a more complete settings package.
- How should I test epigra/nova-settings before using it in production?
- Run a non-production spike: install the package, register the Nova tool, publish migrations and assets, define representative settings, and test create, read, and update behavior. Add CI checks for package discovery, migrations, field rendering, validation, and authorization. Pin the package version, document the tested Nova, Laravel, and PHP matrix, and keep a rollback plan.
- What are alternatives to epigra/nova-settings for Laravel settings management?
- Alternatives include building a small custom Nova tool backed by your own settings table, using a general Laravel settings package with Nova integration, or keeping deployment-level configuration in environment and config files. Choose based on whether you need native Nova editing, auditability, tenant scoping, or secret storage. For a narrow admin-edited settings set, an owned table plus a Nova resource can be simpler to maintain.
- Is epigra/nova-settings maintained and safe for production use?
- The assessment shows no visible community signal: no stars and 0 dependents, so maintenance and long-term compatibility are not proven. That does not prove the code is unsafe, but it means you should budget for internal ownership, Nova upgrade testing, and a possible fork. Do not accept it as a strategic dependency without a compatibility spike, source review, and rollback plan.
Weaver
How can I help you explore Laravel packages today?