Weave Code
Files Laravel Package
laravel-enso/files
File management package for Laravel Enso that adds uploads, browsing, and organization of files and folders, polymorphic attachments, image processing, and ready-to-use Vue components for handling files in Enso applications.
Laravel Enso file management add-on for smoothing out some of common cases found when working with files
Frequently asked questions about Files
- What is laravel-enso/files and what does it do?
- laravel-enso/files is a file management add-on for the Laravel Enso admin-panel ecosystem. It provides uploads, browsing and organization of files and folders, polymorphic attachments, image processing, and ready-to-use Vue components for handling files. It is designed to integrate with Enso conventions rather than serve as a standalone general-purpose file library.
- How do I install laravel-enso/files in a Laravel app?
- In an Enso application, install it with composer require laravel-enso/files, then run the package migrations, publish its config, register the file trait on the models that need attachments, and point your filesystems disk at your storage target. The package is version-locked to enso/core, so pin compatible versions together. A non-Enso Laravel app should expect a rewrite rather than a simple install.
- Does laravel-enso/files work with a standard Laravel app or only Laravel Enso?
- It is built for Laravel Enso, so adoption in a standard Laravel app is a poor architectural fit. You would pull in a large Enso dependency graph or fork and strip out the Enso-specific service and permission layers. For a non-Enso app, treat it as a reference implementation and extract the File model, migration shape, and trait into your own codebase.
- Which Laravel and PHP versions does laravel-enso/files support?
- Enso packages are version-locked to each other and to specific Laravel and PHP versions, typically Laravel 8, 9, or 10 with PHP 8.x for recent Enso releases. Confirm the supported matrix between laravel-enso/files, enso/core, the Laravel major, and the PHP version before committing. The upstream release cadence determines when new Laravel majors are supported.
- How do polymorphic file attachments work with laravel-enso/files?
- The package stores files in a files table with polymorphic fileable linkage plus metadata columns, so a single File model can attach to multiple Eloquent models. You register the provided trait on the models that should accept attachments. This follows Enso's model and table conventions and is the native path inside an Enso application.
- Can laravel-enso/files upload to S3 or other non-local disks?
- Storage behavior depends on Laravel's filesystems configuration, but the package's assumptions about disks, file naming, and deletion semantics should be verified before production use. Confirm that non-local disks such as S3 or GCS are supported cleanly rather than assuming local storage. In an Enso app, point the disk config at your storage target and test upload, browse, and delete flows.
- Does laravel-enso/files handle image processing and thumbnails?
- The package description includes image processing and ready-to-use Vue components for handling files. Whether thumbnails and image transformations are handled inside this package or by a sibling Enso package should be confirmed against the current documentation. Test the specific image operations you need before relying on them.
- How are file permissions and access control enforced in laravel-enso/files?
- Authorization is tied to Enso's permission and menu system, so access control hooks into Enso's ACL conventions rather than being a standalone guard. In a non-Enso app, you would need to re-express access control in your own idioms. Verify how file access is enforced for your use case, especially for direct downloads.
- What happens to files when a parent model is deleted in laravel-enso/files?
- Deletion and cleanup semantics are opinionated and should be verified against your requirements: check whether soft deletes are used, how orphaned files are handled, and whether files cascade when a parent model is deleted. The package aims to smooth over common cases, but those assumptions matter in production. Plan a cleanup strategy for files whose parent records are removed.
- Is laravel-enso/files actively maintained, and what are the alternatives?
- The package is maintained as part of the Laravel Enso ecosystem and has a small adoption footprint outside it, so single-maintainer and release-cadence risk apply. MIT licensing lets you fork, but you inherit maintenance if upstream stalls. For non-Enso apps, consider general-purpose Laravel file and media libraries, or extract the model, migration, and trait patterns into your own internal package.
Weaver
How can I help you explore Laravel packages today?