Weave Code
Nova Config Laravel Package
illuminatech/nova-config
Illuminatech Nova Config is a Laravel Nova tool for managing application configuration from the admin panel. Browse and edit config values in a clean Nova interface, making runtime settings easier to maintain without manual file edits.
A Laravel Nova tool for application configuration management
Frequently asked questions about Nova Config
- What is illuminatech/nova-config used for?
- Illuminatech Nova Config is a Laravel Nova tool for browsing and editing application configuration values from an admin panel. It is intended for non-secret, low-change runtime settings where Nova is already the internal admin surface. It is not a full configuration platform and should not own secrets, high-volume feature flags, or audit-critical controls.
- How do I install illuminatech/nova-config in a Laravel Nova application?
- Install it with Composer, then register the package service provider and Nova tool in your Laravel application. You will typically publish and review any package migrations or config, run migrations, define which keys are editable, and wire authorization. Pin a specific version and start in a non-production environment before promoting it.
- Which Laravel, PHP, and Nova versions does illuminatech/nova-config support?
- The provided context does not list exact supported Laravel, PHP, or Nova versions, so you must verify compatibility against your matrix before adoption. Check the package release history, open issues, and Nova tool conventions for the Nova major version you run. Avoid assuming support for current releases simply because the package installs.
- How does illuminatech/nova-config store and cache configuration values?
- The context does not confirm whether values are stored in database tables, files, or cache, so review the published migrations and source before use. You should also verify how it interacts with Laravel config caching and whether changes invalidate application or config caches. Do not rely on implicit cache clearing until you have tested it in staging.
- Does illuminatech/nova-config support encryption or secret management?
- The tool is best suited to non-secret, low-change configuration and should not be used for credentials or other sensitive values without additional safeguards. The context does not confirm built-in encryption, so verify storage format and access controls before storing anything sensitive. Even with encryption, you would still need authorization, audit, backup, and exposure controls.
- Is illuminatech/nova-config suitable for production use?
- Treat it as a small internal utility rather than a production-critical configuration platform. Adoption signals are weak, and the license is reported as NOASSERTION, so legal and security review are required before production use. Production use should follow a staging pilot, authorization checks, audit logging, backup and restore, and a documented rollback path.
- How do I test configuration changes made through Nova Config?
- Test reads, writes, validation, authorization, and cache invalidation in a non-production environment before promoting changes. Seed a small set of non-sensitive keys and verify that edited values are reflected consistently across requests and deployments. Include Nova upgrade tests because the package is coupled to Nova conventions.
- Does illuminatech/nova-config include audit logging, approvals, or rollback?
- The context does not indicate built-in audit history, approval workflows, or rollback, so assume you must add those controls yourself if they are required. For audit-critical settings, use a first-party settings table or another system with explicit change tracking. At minimum, log who changed which key, when, and from what value.
- What are alternatives to illuminatech/nova-config for Laravel settings management?
- Alternatives include Laravel's native config and environment files, a first-party settings table with your own Nova CRUD screens, or a dedicated settings package that matches your audit and secret-management requirements. Choose based on whether you need simple editable settings or governed configuration with approvals and rollback. Nova Config is only a fit when the scope is small and non-sensitive.
- How do I maintain or replace illuminatech/nova-config if it is abandoned?
- Expect low upstream activity and limited support, so the team should own dependency pinning, Nova upgrade testing, migration review, and replacement planning. Keep a fallback path to env/config files or a first-party settings table, and document rollback before a Nova upgrade. If the package is abandoned, fork it or replace it rather than making it a critical-path dependency.
Weaver
How can I help you explore Laravel packages today?