- Is soft-passio/media-bundle a Laravel package or a Symfony bundle?
- The package name and Bundle suffix suggest a Symfony-style bundle, while the overview describes general PHP media management and the blurb mentions Laravel. The provided context does not include composer.json metadata confirming native Laravel service providers or Symfony bundle registration. Verify framework fit before adopting it.
- What features does SoftPassio MediaBundle provide for media uploads and storage?
- The available context describes centralized media asset management, extensible storage and metadata, uploads for files and images, a unified media model, configurable storage disks, image conversions, Eloquent attachment, cleanup, and metadata support. However, there is no documentation excerpt confirming exact APIs, extension points, or behavior. Treat the feature list as a capability map and verify each item in source and tests.
- Does soft-passio/media-bundle support Laravel 10, Laravel 11, and PHP 8?
- The last release shown is 2020-06-26, so modern Laravel 10/11 and PHP 8.x support is unlikely without work. Composer constraints and framework compatibility are unknown and should be checked in composer.json. Run a sandbox install with Composer audit and static analysis, and expect backporting rather than drop-in support.
- How do I install soft-passio/media-bundle with Composer?
- The expected command is composer require soft-passio/media-bundle, but inspect Packagist metadata and composer.json first. Because the last release is from 2020, dependency conflicts with current PHP, Laravel, and Flysystem versions are likely. Install only in an isolated project until compatibility is proven.
- Does MediaBundle support S3, CDN delivery, image conversions, and queued processing?
- The blurb mentions configurable storage disks and image conversions, but the assessment does not confirm S3, CDN, or queue support. Storage behavior likely depends on the Flysystem version, and the 2020 release predates Flysystem v3. Validate each capability in a sandbox proof of concept before relying on it.
- Is soft-passio/media-bundle maintained and safe for production use?
- High risk. The package has no visible releases since 2020, 0 stars and 0 dependents, and no evidence of tests, CI, or a security history. Adopting it creates an internal maintenance obligation, so fork it with an owner and SLA or use a maintained alternative.
- Does soft-passio/media-bundle have tests and CI?
- The technical assessment states there is no evidence of test coverage or CI. That does not prove the code is broken, but it means you must supply integration tests for uploads, metadata, conversions, cleanup, authorization, and deletion. Require tests and static analysis before any production use.
- How do I attach media to Eloquent models with this bundle?
- The blurb says the bundle provides simple APIs for attaching media to Eloquent models, with support for cleanup and metadata. The exact traits, relationships, disk configuration, and conversion hooks are not documented in the provided context. Inspect the source and write integration tests before relying on the attachment API.
- What are maintained alternatives to soft-passio/media-bundle for Laravel?
- Consider Spatie Laravel Media Library, Plank Laravel Media, or a custom Flysystem-based media service if you need tighter control. Compare Laravel version support, image conversions, S3 and CDN integration, queued processing, deletion behavior, tests, and release cadence. Use MediaBundle as a reference implementation rather than a production dependency unless you are prepared to fork it.
- Can I fork and modernize soft-passio/media-bundle under the MIT license?
- Yes, the MIT license permits forking and modification. Budget for PHP 8.x, Laravel 10/11, Flysystem v3, modern image processing, tests, CI, and a security review before calling it production-ready. Keep the fork in an internally owned repository and expose it behind an internal media-service interface.