- What is juniyasyos/filament-media-manager used for?
- It is a Filament panel plugin for Laravel applications that provides an admin interface for browsing, uploading, and organizing images and media files and folders. It is intended for back-office use where Filament is already the admin framework, not as a public media API or domain-layer dependency.
- How do I install juniyasyos/filament-media-manager in a Laravel Filament app?
- Install it with Composer and register it as a Filament plugin in your panel provider, then publish any config or assets the package provides. Because the release artifacts are thin, pin an exact version and commit the lockfile, and verify published config and migrations in a disposable environment before using a real storage disk. Use the package README for the exact registration snippet rather than guessing it.
- Which Laravel and Filament versions does this media manager support?
- The supplied materials do not state an explicit supported Filament, Laravel, PHP, or database matrix, so do not infer it from the version number. Confirm the supported matrix with the maintainer or by testing in a sandbox against your exact Filament major and Laravel version before adoption.
- Does filament-media-manager depend on Spatie Media Library?
- The available evidence does not confirm whether it depends on Spatie Media Library or uses its own persistence. Check composer.json and the published models and migrations before adopting it. Architecturally, the media library and filesystem config should own disks, paths, and conversions, while this package should own only the management UI.
- Is filament-media-manager safe to use in production?
- It can be reasonable for internal admin use if you gate adoption on verification, because a media manager handles uploads and deletions where defects can destroy content or expose files. Before production, test upload, browse, attach, delete, and permission-denied paths on a non-production disk, and define disk, retention, and authorization policies. Resolve version provenance and the supported Filament and Laravel matrix first.
- How do I configure storage disks for uploads in this Filament media manager?
- Storage is expected to be controlled through Laravel filesystem disks and the underlying media library configuration, not by application services. Decide local versus S3-compatible storage, document retention, and exercise uploads and deletions against a non-production disk before enabling real users. Inspect the published config for the actual disk option name rather than assuming one.
- Does juniyasyos/filament-media-manager support multi-tenancy?
- Multi-tenancy support is not established by the provided materials, so do not assume tenant isolation. If multiple tenants share a media manager, verify whether the package assumes a single global library and whether authorization scopes browsing and deletion per tenant. Treat tenant isolation as a gating requirement and test cross-tenant access paths.
- Are uploads validated and are deletions soft or hard in this package?
- Server-side upload validation, MIME restrictions, and whether deletions are soft or hard are not confirmed by the release artifacts. Because this is an admin-plane media manager, define validation and authorization policy yourself and test permission-denied paths. Do not rely on client-side controls for file type restrictions or deletion safety.
- What should I check before upgrading from 3.0 to v1.4.1?
- Treat 3.0 to v1.4.1 as a greenfield install rather than a semver-safe upgrade, because the compare link has no enumerated changes or migration notes and the version scheme is inconsistent. If an environment already runs the 3.0 tag, freeze it, diff the published config and migrations between the two refs, and only then plan a move.
- When should I use an alternative to this Filament media manager?
- Use this package when Filament is already your admin framework and the media need is internal or back-office. If media is surfaced to end users outside Filament, use the underlying media library directly and keep this as an operator tool. Otherwise evaluate maintained Filament media plugins against the same supported-version, tenancy, and deletion-safety checks.