Weave Code
Documents Laravel Package
laravel-enso/documents
Laravel Enso Documents provides document management for Enso applications, letting you upload, store, organize, and attach files to models, with template support, permissions, and ready-made UI integration.
Laravel Enso Document Uploader and Manager package, meant to help you attach, download, remove and keep track of the user's files
Frequently asked questions about Documents
- What is laravel-enso/documents used for?
- laravel-enso/documents is an Enso ecosystem module for uploading, storing, organizing, downloading, and removing files attached to records in a Laravel Enso admin application. It is designed for back-office document workflows with template support, permissions, and ready-made UI integration. It is not a standalone document-management product or a good fit for API-first or non-Enso applications.
- How do I install laravel-enso/documents in a Laravel Enso app?
- Install it with Composer, run the package migrations, configure your storage disk, and wire the Enso menu and permissions. Then attach the document behavior to the models that should own files and validate upload, download, and delete against one test entity. For existing Enso apps, align package, Enso Core, and frontend versions before broad adoption.
- Which Laravel, PHP, and Enso Core versions are supported by laravel-enso/documents?
- The provided context does not list exact Laravel, PHP, or Enso Core version constraints. Check the package composer.json and test against your target Enso Core release before installing. Pin versions explicitly and treat Enso Core upgrades as coordinated releases rather than incidental Composer updates.
- Can I use laravel-enso/documents in a non-Enso Laravel application?
- It is an Enso ecosystem module, so using it outside Laravel Enso is high-friction and likely not worth the integration effort. Non-Enso applications should evaluate alternatives such as Spatie Media Library or a custom attachment layer. If you need document management without Enso, choose a standalone package or build a thin attachment service.
- How do I attach documents to Eloquent models with laravel-enso/documents?
- The package is intended to attach the document behavior to selected Eloquent models in an Enso application, letting users upload and track files against domain records. Validate the exact relationship type, whether one model can have multiple documents, and what metadata is stored by reviewing the migrations and model traits for your package version. Start with one low-risk entity before rolling it out broadly.
- Does laravel-enso/documents support private storage, S3, and signed URLs?
- The package integrates with Laravel storage configuration, but the context does not confirm every disk, URL, or thumbnail feature. Verify local and S3 or object-storage behavior in a sandbox before production. For production, confirm private storage, signed download URLs, file size limits, MIME validation, and thumbnail support if your use case requires them.
- How are permissions and download authorization handled in laravel-enso/documents?
- Enso applications wire menu entries and permissions for document actions, and you should define policies for upload, view, download, and delete. Do not rely on UI hiding alone; enforce download authorization server-side. Review tenant isolation and access rules before exposing documents to customer-facing users.
- What happens to files when a parent record is deleted in laravel-enso/documents?
- The provided context does not specify cascade deletion or orphan cleanup behavior, so test parent-record deletion explicitly. Define retention, GDPR deletion, and orphan cleanup jobs for files that should not remain in storage. Also plan checksum-verified backfills if you migrate existing documents into the package.
- Is the Vue/Enso UI required, or does laravel-enso/documents provide API endpoints?
- The intended integration is the Enso Vue UI, with menu, permissions, and ready-made frontend support. The context does not confirm API endpoints for headless or non-Enso clients. If you need public APIs or a separate frontend, expect custom API work or choose a different document package.
- What are alternatives and maintenance concerns for laravel-enso/documents?
- Alternatives include Spatie Media Library or a custom attachment layer, especially for non-Enso Laravel applications. laravel-enso/documents has low community adoption and is coupled to Enso Core, so your team should own upgrade testing, patches, documentation, and security review. Treat it as a conditional accelerator inside Enso, not a strategic platform.
Weaver
How can I help you explore Laravel packages today?