Weave Code
File Manager Laravel Package
proside/file-manager
Reusable file manager for Laravel 10/11/12 built in Livewire v4: directory tree, grid/list views, uploads, drag & drop, trash with restore, previews, search, multi-disk support and a file picker component. No iframe or external service.
Proside File Manager is a reusable file manager for Laravel 10/11/12, built entirely with Livewire v4. It replaces the old Next.js/React version with full feature parity while running inside your Laravel app—no iframe, no JWT, no external service—using your existing auth and session.
- Directory tree with lazy-load, grid/list views, filters, sorting and breadcrumbs
- Upload via FAB or drag & drop; move items (including multiples) between folders
- Trash (
apagados) with configurable retention, restore and permanent delete - Image/video lightbox preview and functional name search
- File picker for forms (
<x-file-manager::picker>), multi-disk support and PT/EN translations
Frequently asked questions about File Manager
- Does proside/file-manager require Livewire 4?
- Yes. The package declares a hard livewire/livewire ^4.0 constraint and targets Laravel 10.49+ with PHP 8.1+. If your application is still on Livewire 3, adoption means scheduling a framework-wide major upgrade rather than simply installing a package. Confirm your host app's Livewire version before planning integration.
- How do I install proside/file-manager in a Laravel app?
- Run composer require proside/file-manager; package discovery registers the service provider, routes, Livewire component and Blade components automatically. Create the storage symlink with php artisan storage:link, then optionally publish the config, views, lang and assets using the documented vendor:publish tags. If your app compiles Tailwind, add the package view path to your tailwind.config.js content array so the utility classes are generated.
- Can I use proside/file-manager in a non-Livewire Laravel app?
- No, the file manager is a Livewire component that renders through Livewire's request lifecycle, so it is not a library you can wrap from Blade controllers, Inertia/Vue or API-first stacks. The no-iframe benefit only applies if the host app is already a Livewire shop. In a non-Livewire app you gain none of the architecture advantage and still inherit Livewire's constraints.
- How do I embed the file picker in a form?
- Use the Blade component <x-file-manager::picker> as the integration point for forms. Before committing, confirm the picker's return contract (path, disk-qualified key, or array of selections) and verify it matches the path or URL format already persisted in existing records. Your form code will bind directly to that contract, so it is worth validating early.
- Does proside/file-manager support S3 and multiple disks?
- Yes. The package uses Laravel's Filesystem abstraction, so local, public and S3 disks work through configuration without code changes. Publish config/file-manager.php to point it at the disk you want. Note that on S3 a move is copy plus delete and is not atomic, which matters for drag-and-drop moves and trash operations.
- How does the trash work and does it need a cron job?
- Deleted items go to a physical apagados folder with a configurable retention period and automatic expiry, and you can restore items or delete them permanently. Because the trash is folder-based rather than a DB-backed soft delete, plan for double storage and non-atomic move semantics on remote disks. Confirm who actually runs expiry in your deployment and whether the job is idempotent before relying on it.
- Is proside/file-manager safe for production and does it handle authorization?
- The package uses your existing auth and session, but authentication is not authorization: per-folder ACLs, tenant isolation and read-only roles are not in the documented feature list. Before any external-facing deployment, review upload-time validation (MIME sniffing, SVG/HTML handling, filename sanitization, path traversal) and whether previews are signed or publicly exposed. Also load-test large uploads, since Livewire routes them through temporary storage and PHP/webserver limits with no documented chunked or resumable support.
- What Laravel and PHP versions does proside/file-manager support?
- It targets Laravel 10/11/12 and requires PHP 8.1+, with Laravel 10.49 called out as the baseline. It also requires Livewire ^4.0, which is the hardest constraint in the matrix. Pin the exact package and livewire/livewire versions and check what the package actually CI-tests against before upgrading other dependencies.
- How do I handle large file uploads with Livewire in this file manager?
- Uploads are synchronous through Livewire's temporary storage, so PHP upload_max_filesize, post_max_size and webserver body limits apply. The README does not mention chunked or resumable uploads, queueing, or server-side size ceilings, so large-file support is unproven and should be load-tested rather than assumed. If you need big files, add your own validation and consider offloading uploads outside the component.
- Is proside/file-manager actively maintained, or should I look for alternatives?
- It is an internal-origin package with a single named maintainer, zero stars and zero dependents, so treat it as a vendored internal dependency rather than a community library. Budget for the possibility that your team becomes the maintainer, and pin versions to limit churn from the Livewire v4 coupling. If you are not already on Livewire 4, a separate service or a more established package may be a lower-risk alternative.
Weaver
How can I help you explore Laravel packages today?