Weave Code
Sonata Media Bundle Laravel Package
mediamonks/sonata-media-bundle
A MediaMonks-maintained Symfony bundle based on Sonata Media Bundle for managing uploaded media, image thumbnails, and storage providers. It supports Sonata Admin integration and flexible asset handling for PHP projects that need a familiar media management workflow.
An alternative media bundle for Sonata Admin
Frequently asked questions about Sonata Media Bundle
- Can I use mediamonks/sonata-media-bundle in a Laravel application?
- No. Despite sometimes being listed with PHP packages, mediamonks/sonata-media-bundle is a Symfony bundle built for the Sonata Admin ecosystem and cannot be installed or used in a Laravel app. If your stack is Laravel, evaluate spatie/laravel-medialibrary or a small custom media service instead. This package only makes sense in a Symfony project already using Sonata Admin and Doctrine ORM.
- How do I install mediamonks/sonata-media-bundle?
- Install it with Composer, register the bundle in your Symfony kernel or bundles configuration, and wire up the required Doctrine entities and Sonata Admin classes. You will also need to configure a Flysystem-backed storage adapter and your image filter or thumbnail settings. Before installing, confirm the package's PHP, Symfony, Sonata Admin, Doctrine, and Flysystem version constraints match your project.
- What are the requirements for mediamonks/sonata-media-bundle?
- It expects a Symfony application, Sonata Admin as the admin backbone, Doctrine ORM for persistence, a Flysystem-backed storage layer, and an image-derivative or thumbnail dependency. The bundle is designed around Sonata Admin integration, so it is not a standalone media library. Check the exact version constraints during a spike, because a mismatch could force unrelated upgrades.
- How is mediamonks/sonata-media-bundle different from sonata-project/media-bundle?
- It is positioned as an alternative to SonataMediaBundle with a leaner, more configurable media model rather than a heavy, opinionated one. The value is architecture simplification for teams already using Sonata Admin, not a net-new media capability. It is designed to be subclassed, so entities, admin classes, and storage contracts should be overridable, but you must verify that before adopting.
- Does mediamonks/sonata-media-bundle support Symfony 6 and Symfony 7?
- Support is not guaranteed just because the package exists, and a low-adoption bundle is unlikely to track Symfony 6 to 7 and Sonata Admin 4 to 5 promptly. Review the Composer constraints and commit history to see which versions are actually supported. If adoption forces a Symfony or Sonata upgrade you were not already planning, decline and keep your current media stack.
- How do I configure storage providers, a CDN, or custom thumbnails?
- Storage is expected to be Flysystem-backed, so you configure the adapter in the bundle configuration and can add a CDN adapter if the storage contracts are cleanly extensible. Thumbnails and image derivatives are handled through image-filter configuration. Confirm during the spike that you can add your custom derivative pipeline without forking the bundle.
- Is mediamonks/sonata-media-bundle actively maintained?
- Adoption signals are the main risk: the project has roughly 10 stars and zero Packagist dependents, and it is maintained by a single vendor. Check the last 12 to 18 months of commits, open-issue ratio, and maintainer responsiveness before relying on it. Treat it as a vendored fork under explicit internal ownership rather than a community-supported dependency.
- How do I migrate existing media from sonata-project/media-bundle?
- There is no guarantee of documented migration tooling, so assume you own the data migration. You will need to move media records, storage keys, and derivative URLs without breaking published content. Plan and test this carefully, because migration correctness is a medium-to-high risk even when the integration itself is straightforward.
- Can I extend the media entities, admin forms, and thumbnail pipeline?
- The bundle is designed to be subclassed, so entity extension, Sonata Admin form wiring, and image-filter configuration should be possible. The make-or-break detail is whether those contracts are cleanly overridable without forking. Validate entity, storage adapter, and admin form extensibility in a non-production branch before committing.
- Is mediamonks/sonata-media-bundle safe for production, and how is it tested?
- The license is MIT, but there is no obvious upstream security response process, so you would own vulnerability triage if you adopt it. Review test coverage and CI status to see whether a green build is a trustworthy regression signal. Given the low adoption, a production rollout should include a vendored fork, internal ownership, and a realistic three-to-five-day integration spike first.
Weaver
How can I help you explore Laravel packages today?