Weave Code
Nova File Manager Laravel Package
bbs-lab/nova-file-manager
A file manager for Laravel Nova that lets you browse, upload, organize, and manage files and folders directly inside your Nova admin panel. Provides a clean interface for common file operations, making media and document management easy without leaving Nova.
The most advanced File Manager for Laravel Nova, feature rich and robust build.
Frequently asked questions about Nova File Manager
- How do I install bbs-lab/nova-file-manager in Laravel Nova?
- Install it with Composer using composer require bbs-lab/nova-file-manager, then register the tool in your NovaServiceProvider's tools() method. Publish the package config file and define one or more named Flysystem disks that the file manager is allowed to expose. Typical integration is a day-scale effort on a project that already runs Nova, but plan extra time for hardening which disks and operations are enabled.
- Which Laravel, PHP, and Nova versions does this file manager support?
- The package is built as a Laravel Nova tool, so it depends on a commercial Nova license in addition to Laravel and PHP. The README excerpt here does not publish a supported version matrix, so verify the exact Laravel, PHP, and Nova major versions against the repository's composer.json and CI configuration before adopting it. Nova tools lean on Nova's internal front-end stack, which is why major Nova releases are the main compatibility risk.
- How do I restrict the file manager to specific disks or a single folder?
- Access is driven by the Flysystem disks you configure, so the safest approach is to publish the config and expose only the disks and roots you intend. Keep sensitive disks read-only or omit them entirely, and avoid pointing the tool at a publicly web-served directory unless you have verified the upload restrictions. Whether a per-disk single directory root can be enforced should be confirmed in the source rather than assumed from the README.
- Is bbs-lab/nova-file-manager safe against path traversal and malicious file uploads?
- A file manager that writes to a web-served disk is a potential remote-code-execution vector, so treat security review as mandatory before production use. Check that the tool canonicalizes target paths, defends against ../ traversal and symlink escape, and enforces extension or MIME allowlisting in code. Ideally confirm there are feature tests covering those cases, and disable write operations on any disk that serves PHP or other executable content.
- Does it respect Nova authorization, or is access all-or-nothing?
- The tool registers through Nova's tool lifecycle, so it inherits Nova's authentication and gating at the tool level. Per-operation control (browse, upload, rename, move, copy, delete, zip and extract) is a separate question and should be verified in the source rather than assumed. If you need granular file-level ACLs, expect to engineer that around the tool with a custom policy or a wrapper.
- Does the file manager work with S3 and other object storage disks?
- Because it operates over a configured Flysystem disk, it should work with any driver Laravel's filesystem supports, including S3. Object stores behave differently from local disks for renames, directory semantics, and large uploads, so test the specific operations you rely on. Chunked or resumable upload support for S3 in particular is worth confirming before committing.
- Are large file uploads chunked or resumable?
- Whether uploads are sent in a single request or chunked determines timeout and memory behavior at scale, and the documentation does not settle it. Verify upload limits and the request strategy in the code or by testing against your largest realistic asset. If you routinely handle very large media, confirm the behavior on your target disk before rollout.
- Does it store file metadata, audit trails, or versioning?
- No. The package presents a UI over files on disk and owns no persistent metadata layer, so there is no first-class record of who uploaded what, when, or with which tags. Requirements for audit trails, file-level ACLs, versioning, or polymorphic attachments have to be engineered around the tool. That also means there are no migrations or schema coupling to worry about.
- What happens when Laravel Nova ships a new major version?
- Nova tools rely on Nova's internal front-end stack and asset conventions, so a Nova 5 or 6 bump can break the tool until the maintainer publishes an update. bbs-lab appears to be a small or single-maintainer project, and the Nova market itself is paid and therefore small, so release cadence is a real risk over a 12 to 24 month horizon. Pin your Nova and tool versions and test upgrades in staging before applying them.
- Is this file manager worth it if I don't already use Nova, or are there free alternatives?
- The package is MIT licensed but requires a paid Nova license, so its value is gated on a platform you already pay for. If Nova is deployed, the marginal cost is low and the ROI is strong; if it is not, do not adopt Nova solely to use this tool, because total cost includes the license plus security hardening and maintenance. Standalone Laravel file managers or a custom Flysystem-based admin screen are reasonable alternatives if you are not on Nova.
Weaver
How can I help you explore Laravel packages today?