- Can I use this bundle in a Laravel project without Symfony?
- Technically possible but not seamless. The bundle relies on Symfony components (Doctrine ORM, EasyAdmin) and would require translating Symfony services to Laravel’s ecosystem. You’d need to replace EasyAdmin with a Laravel admin panel (e.g., Filament) and adapt Doctrine models to Eloquent. Start by evaluating the effort vs. native Laravel alternatives like Spatie Media Library.
- What Laravel versions does this bundle support?
- The bundle is Symfony-focused, so no official Laravel support exists. However, you could integrate Symfony components (e.g., `symfony/http-foundation`) into Laravel 8+ via service providers. Test compatibility with your Laravel version’s PHP requirements (e.g., 8.0+). No guarantees exist for long-term Laravel version alignment.
- How do I handle image derivatives (thumbs, medium, highres) in Laravel?
- The bundle uses Symfony’s image processing, which won’t natively integrate with Laravel’s `spatie/laravel-medialibrary` or `intervention/image`. You’d need to either: 1) Fork the bundle to replace derivative logic with Laravel-compatible libraries, or 2) Use Laravel’s queue system (e.g., Horizon) to process derivatives separately after uploads.
- Is EasyAdmin required, or can I use a Laravel admin panel instead?
- EasyAdmin is tightly coupled to the bundle’s admin features. To replace it, you’d need to rebuild the CRUD interfaces in Laravel (e.g., with Filament or Backpack). The bundle’s backend logic (categories, uploads) would still work if you adapt the controllers/services. Expect 1–2 weeks of dev time for a full migration.
- Does this bundle support batch uploads and large files?
- The bundle supports batch uploads, but its Symfony-based architecture may lack Laravel’s optimized queue systems (e.g., Horizon). For large files, consider integrating Laravel’s chunked uploads or queueing the bundle’s upload logic via Laravel’s `bus` facade. Test with your expected file sizes before production.
- Are there Laravel-native alternatives with similar features?
- Yes. For galleries, compare `spatie/laravel-medialibrary` (media management) + `filament/spatie-media-library-panel` (admin UI). For batch uploads, `laravel-filemanager` or `dropzone.js` with custom logic may suffice. These avoid Symfony dependencies entirely and integrate natively with Laravel’s Eloquent and queues.
- How do I install this in Laravel despite Symfony dependencies?
- Start by requiring Symfony components via Composer (e.g., `symfony/console`, `symfony/options-resolver`). Register them in Laravel’s `config/app.php` under `providers`. For Doctrine, use a hybrid approach: either proxy entities to Eloquent or replace Doctrine with Laravel’s database layer. Document each dependency’s Laravel integration path.
- What’s the maintenance risk of using this bundle in Laravel?
- High. The bundle has no active maintenance (0 stars, 1 dependent) and lacks tests or CI/CD. Symfony updates may break Laravel compatibility. Plan to fork and maintain it yourself or replace it with a Laravel-native solution (e.g., Spatie + Filament) within 6–12 months to avoid technical debt.
- Can I use this bundle alongside existing Laravel media libraries?
- No, direct conflicts will arise. The bundle manages its own database schema (categories, media, derivatives) and image processing pipeline. To coexist, you’d need to either: 1) Isolate the bundle in a microservice, or 2) Replace its media logic with Laravel’s libraries (e.g., Spatie) and adapt the bundle’s controllers to use your preferred storage system.
- Are there performance concerns for production use?
- Potential issues include: Symfony’s event system not aligning with Laravel’s, Doctrine queries requiring Eloquent translation, and derivative generation blocking requests if not queued. Test under load with your expected traffic. Mitigate risks by offloading image processing to queues (e.g., Laravel’s `dispatch()`) and monitoring memory usage during batch uploads.