- What is wotz/filament-media-library used for?
- wotz/filament-media-library is a Filament plugin for Laravel panels that adds a media manager UI for uploads and browsing, with Spatie Media Library integration for attaching files to models. It is aimed at panels that need a shared, reusable media pool rather than per-record upload fields. The package is low-adoption, so validate its feature set against the source before committing.
- How do I install wotz/filament-media-library in a Laravel Filament panel?
- Install it with Composer via composer require wotz/filament-media-library, then publish any config, migrations, or assets with php artisan vendor:publish and register the plugin on your Filament panel provider. Because the README excerpt is not available here, confirm the exact plugin registration class and publish tags in the repository. Run migrations only after checking whether the package owns schema or reuses Spatie's media table.
- Which Filament, Laravel, PHP, and Spatie Media Library versions does it support?
- The package sits at the intersection of Filament, Spatie Media Library, Laravel, and PHP versions, and small plugins typically support only a narrow band. The available context does not list exact constraints or CI coverage, so check composer.json and the release/tag history before installing. Treat any unverified Filament v3 versus v4 compatibility as a spike task, not an assumption.
- Does it reuse Spatie Media Library's media table or create its own migrations?
- The package is described as Spatie Media Library integration, which suggests it likely reuses Spatie's media table, but that is not confirmed. Check the package migrations and models to see whether it adds its own tables; reusing Spatie's schema is much cheaper to abandon than adopting a new schema commitment. If it ships migrations, review them as part of diligence before production.
- Does it provide a shared media browser or just wrap Filament's SpatieMediaLibraryFileUpload field?
- The stated value is a ready-to-use media manager with uploads and browsing, not just a re-skin of Filament's SpatieMediaLibraryFileUpload field. The key evaluation is whether it exposes a shared media browser or modal with cross-model reuse; if it only wraps the built-in field, it may be redundant. Inspect the plugin's resources, pages, and form components to confirm.
- Is it safe to use in production given the low star count and no dependents?
- Low stars and zero dependents mean there is little ecosystem proof, not necessarily poor quality, but it shifts the decision to owning a small codebase. For production, pin exact versions, review the source, and be prepared to fork under MIT if maintenance stalls. Run a spike in a staging panel before relying on it for admin media workflows.
- Does it handle upload security like MIME validation, SVG sanitization, and private disk authorization?
- Media upload packages must handle MIME validation, SVG/HTML sanitization, private-disk authorization, and URL scoping, and small packages often under-deliver here. The context does not confirm the package's security posture, so review its validation rules, disk configuration, and policy/authorization hooks explicitly. Do not assume Filament or Spatie defaults cover every upload path.
- Does it support Filament multi-tenancy and per-tenant media scoping?
- Filament supports native multi-tenancy, but small plugins do not always respect tenant-aware disk paths or query scoping. Verify whether wotz/filament-media-library scopes media queries and storage paths by tenant, and test with two tenants in a staging panel. If it does not, you may need to add scoping or avoid it in multi-tenant panels.
- Is there a test suite or CI to verify the package before adoption?
- The available context does not confirm a test suite, CI matrix, or coverage of authorization and upload validation. Ask for or inspect tests for panel registration, media browsing, upload validation, and tenant scoping before adoption. If tests are missing, budget for a fork-and-own evaluation with your own smoke tests.
- What are alternatives to wotz/filament-media-library for Filament media management?
- Alternatives include Filament's built-in SpatieMediaLibraryFileUpload field for per-record uploads, building a small custom media browser over Spatie Media Library, or evaluating more established Filament media manager plugins. Choose based on whether you need a shared media pool versus simple record attachments. Compare maintenance signal, Filament version support, and security review effort, not just feature lists.