- What is stepanenko3/nova-filemanager used for?
- It is a Laravel Nova tool that adds a file manager to the Nova dashboard. It lets administrators browse, upload, rename, move, and delete files and folders on configured Laravel filesystem disks. It is meant for ad hoc admin and ops file handling, not as a replacement for structured Laravel resource uploads.
- How do I install Nova File Manager in Laravel Nova?
- Install it with Composer, publish its config and front-end assets, then register the tool in your NovaServiceProvider tools method. You should install it on a branch and pin your Nova and Laravel versions before enabling it. The provided overview does not include exact commands, so validate against the package README and your Nova version.
- Which Laravel and Nova versions does Nova File Manager support?
- The provided evaluation assumes Laravel 10 or 11, PHP 8.1+, and Nova 4.x or 5.x, but it does not include a tested compatibility matrix. The last release noted is 2024-03-28, so compatibility with current Nova and Laravel releases is unverified. Confirm your Nova major and test installation in a non-production branch first.
- How do I configure which disks Nova File Manager can access?
- The package is built on Laravel's filesystem abstraction, so it should use disks configured in config/filesystems.php. The key question is whether it exposes every configured disk by default or requires an explicit allow-list in its own config. Inspect the published config before enabling it and scope it to a dedicated disk with a limited root.
- Is Nova File Manager safe to use in production?
- Treat it as a high-risk admin tool until you verify authorization, disk scoping, path traversal protection, upload validation, and delete behavior. File browse, upload, rename, move, and delete from an admin panel need more than an is-a-Nova-user check. Use a dedicated disk, a dedicated gate, and a pilot admin group before wider rollout.
- Can I restrict Nova File Manager access to specific users or roles?
- The overview does not state which authorization primitive gates the tool, so you should not assume per-user or per-disk restrictions are built in. Register the tool behind a dedicated Laravel gate or policy and grant it only to a pilot admin group. If per-disk restrictions are required, verify them in code or add your own scoping layer.
- Does Nova File Manager protect against path traversal on rename and move?
- The provided evaluation flags path traversal and disk escape as high-risk areas for rename and move operations, but it does not confirm that protection is implemented or tested. Before production use, review or test canonicalization and verify operations cannot resolve outside the configured root. This is especially important if users can supply file or folder names.
- Does deleting a file in Nova File Manager go to trash or permanent delete?
- The evaluation says delete appears permanent unless the package has a trash or soft-delete concept, and it does not mention audit logging. Confirm the behavior on a non-production disk before giving anyone delete access. If recoverability or audit trails are required, add backups or avoid granting destructive permissions.
- Does Nova File Manager work with S3 or remote filesystem disks?
- It is built on Laravel's Storage::disk abstraction, so it can theoretically target local, S3, and other configured disks without new drivers. The provided material does not confirm remote-disk support or test coverage. Validate upload, rename, move, and delete behavior against your target disk before relying on it.
- Is stepanenko3/nova-filemanager actively maintained and where is the repository?
- The provided evaluation lists the repository as unknown, which is a real maintenance and security red flag. It also notes a last release date of 2024-03-28 and low adoption, with no visible issue tracker or path to report security fixes. If you adopt it seriously, vendor or fork the code and establish your own maintenance plan.