- How do I install oneduo/nova-file-manager in Laravel Nova?
- Install it with Composer using composer require oneduo/nova-file-manager, then register the tool in your NovaServiceProvider tools() method. Publish the config and frontend assets with vendor:publish, then point the tool at one or more configured Laravel filesystem disks. You must already have a valid Laravel Nova installation and license; this is a Nova tool, not a standalone Laravel package.
- Which Laravel, PHP, and Nova versions does oneduo/nova-file-manager support?
- The 1.0.0 line is assumed to target Laravel 9–11, PHP 8.1+, and Nova 4.x/5.x, but you should verify the exact Composer constraints before committing. Nova major releases have historically introduced breaking frontend changes that tools must follow, so confirm compatibility with your pinned Nova version. Check the package composer.json and release tags rather than assuming support from the README.
- Does oneduo/nova-file-manager support multiple storage disks and S3?
- Yes, the tool is designed to browse and manage files across multiple configured storage disks, including local and S3-style disks, because it sits on top of Laravel's filesystem abstraction. Confirm whether S3 uploads use presigned or direct uploads or proxy through PHP, since that affects performance and upload limits. You configure the available disks in the published config file.
- Is oneduo/nova-file-manager free, or does it require a paid Nova license?
- The package itself is MIT licensed and free to install, but it requires Laravel Nova, which is a separate paid product with its own license cost. Budget for Nova as part of the total cost of ownership. The package license does not include Nova or reduce Nova's licensing requirements, and MIT means the package comes with no warranty or vendor support.
- What changed between v0.16.0 and v1.0.0, and is it a breaking change?
- Version 1.0.0 is a stability declaration: the maintainer is signaling that the public API is considered stable after the 0.x series. The release note is only a link to the v0.16.0...v1.0.0 compare view, with no changelog body or breaking-change list, so you must read the diff to assess upgrade impact. Because 0.x was explicitly unstable, config keys, disk/path conventions, or Nova field names adopted during a 0.x pilot may have changed at this boundary; back up customizations and re-publish carefully.
- How do I control who can upload, rename, move, or delete files in the file manager?
- Authorization is expected to follow Nova's conventions, using Nova policies, gates, and the tool's own authorization hooks rather than relying on the UI alone. For per-tenant or per-role folder isolation, review the package's authorization code and the upload and path-resolution paths, especially after a major version bump. Do not assume README-level documentation covers your isolation requirements; test with real non-admin users.
- What are the upload size limits and file validation rules?
- Upload limits are shaped by your PHP and web server settings such as upload_max_filesize, post_max_size, and timeouts, plus any validation rules exposed by the package config. A file manager is an upload endpoint, so review extension and MIME validation in the code rather than trusting defaults. Test large files, unusual extensions, and slow uploads in a staging environment before production.
- Is oneduo/nova-file-manager actively maintained and safe to depend on in production?
- The package is a small-maintainer project with around 159 stars at the time of assessment, and the move from v0.16.0 to v1.0.0 is a positive lifecycle signal that the API is now considered stable. Post-1.0 breaking changes should arrive as a 2.0 release, which makes a pin-and-track dependency policy easier than under 0.x. Still, check recent commit and issue activity, and be prepared to read diffs when Nova ships a major release.
- How do I test uploads and authorization when using oneduo/nova-file-manager?
- There is no guarantee of comprehensive test coverage on the upload and authorization paths, so add your own feature tests around disk configuration, allowed file types, and policy enforcement. Test that unauthorized roles cannot upload, rename, move, or delete files, and that path traversal attempts are rejected. Run these tests after every package or Nova upgrade, not just at initial installation.
- What security risks should I review before using a file manager in Laravel Nova?
- Treat any file manager as an upload endpoint, a path-resolution engine, and an authorization boundary, and review path traversal protections, extension and MIME validation, and tenant or role folder isolation in the code. A major version bump is exactly when authorization code may have been reworked, so review the v0.16.0...v1.0.0 diff as well as the current state. MIT licensing means no warranty, so security ownership stays with your team.