Weave Code
Nova Filemanager Laravel Package
clevyr/nova-filemanager
Clevyr Nova Filemanager is a Laravel Nova tool for browsing, uploading, organizing, and managing files from your admin dashboard. It provides a simple file manager interface for handling folders and assets without leaving Nova. Use it to view, rename, delete, and upload files and folders directly wi...
At a glance
Frequently asked questions about Nova Filemanager
- What is clevyr/nova-filemanager used for?
- It is a Laravel Nova tool for managing files and folders from the Nova admin dashboard. You can use it to browse, upload, rename, delete, and organize assets without leaving Nova. It is intended for teams already using Laravel Nova, not as a standalone Laravel file manager.
- Does clevyr/nova-filemanager require Laravel Nova?
- Yes. This package is a Nova tool, so it only fits Laravel applications that already use Laravel Nova. It also carries Nova's commercial licensing and upgrade cadence as a hard dependency. It is not a general-purpose Laravel file manager.
- Is clevyr/nova-filemanager v5.0.0 compatible with Nova 4?
- The v5.0.0 release is explicitly aligned to Nova 5.0, and the major version bump strongly suggests Nova 4 support was dropped. The sparse release notes do not confirm whether any Nova 4 compatibility remains. Treat v5.0.0 as Nova 5-only until you verify composer constraints or hear from the maintainer, and keep Nova 4 applications on the v4.x line.
- How do I install clevyr/nova-filemanager in Laravel Nova 5?
- Install it with Composer in a Laravel application that already runs Nova 5, then register the tool in your Nova service provider according to the package README. Complete the Nova 5 upgrade first, because the package version should not be upgraded ahead of Nova. Validate composer constraints and follow any asset or config publishing steps in staging before production.
- What Laravel and PHP versions does clevyr/nova-filemanager support?
- The provided release notes do not list the exact Laravel and PHP version constraints for v5.0.0. Check the package composer.json and README for the supported matrix before scheduling an upgrade. Because this is a major release, verify constraints in staging rather than assuming they match v4.1.1.
- Do I need to publish assets or config after upgrading to v5.0.0?
- The release note mentions Nova 5.0 support and general house-keeping but does not detail asset or config publishing changes. After upgrading, compare your published files with the package documentation and republish only if instructed. Test the Nova tool assets in staging to catch missing or stale files.
- How should I test file uploads and permissions after installing?
- Run smoke tests against each configured storage disk used by the file manager. Test browsing, uploading, renaming, deleting, and authorization flows for the roles that will use the Nova tool. Because the tool touches storage paths and permissions, verify regressions before rolling out to production.
- Can I use clevyr/nova-filemanager as a general Laravel file manager?
- No. It is built as a Laravel Nova tool for the Nova admin dashboard and is not positioned as a general-purpose Laravel file manager. Your application must already use Nova, and the package version must match your Nova major version. Teams without Nova should evaluate a standalone Laravel file manager instead.
- What changed between clevyr/nova-filemanager v4.1.1 and v5.0.0?
- The release note describes Nova 5.0 support and general house-keeping, but the provided information does not document specific changes. A major version bump means you should assume breaking changes until proven otherwise, including dependency, route, config, or asset pipeline changes. There is no documented upgrade guide from v4.1.1 to v5.0.0 in the provided context.
- What are my options if I am still on Laravel Nova 4?
- Stay on the clevyr/nova-filemanager v4.x line unless the maintainer confirms Nova 4 compatibility in v5.0.0. You can also evaluate other Nova-compatible file manager tools, but any replacement should be checked against your Nova version, Laravel version, PHP version, and storage requirements. Do not upgrade the package independently of the Nova upgrade.
Weaver
How can I help you explore Laravel packages today?