Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Media Bundle

Media Bundle Laravel Package

oosaulenko/media-bundle

A PHP media bundle for managing uploaded images and files in Symfony applications, with reusable media entities, storage handling, and thumbnail support for common content workflows. Provides a lightweight foundation for integrating media management into existing projects.

View on GitHub
Deep Wiki
Context7

At a glance

Frequently asked questions about Media Bundle
Is oosaulenko/media-bundle a Laravel package or a Symfony bundle?
It is a Symfony bundle. The package is described as a PHP media bundle that plugs into Symfony applications and provides reusable media entities, storage handling and thumbnail support. Laravel developers evaluating it should know there is no Laravel service provider, facade or config publishing in the package as described. Treat it as a Symfony component, not a Laravel one.
Can I use oosaulenko/media-bundle in a Laravel application as-is?
Not as a drop-in solution. The bundle depends on Symfony bundle registration and Symfony-style service wiring, which Laravel does not load automatically. You would have to write your own integration layer or bridge the underlying storage and entity classes into Laravel's container. For most Laravel projects, a Laravel-native media package will be significantly less work.
How do I install oosaulenko/media-bundle with Composer?
Install it with composer require oosaulenko/media-bundle, then register the bundle in your Symfony bundles configuration so its services are loaded. Check the README and composer.json for the exact bundle class name, required PHP and Symfony constraints, and any configuration you must supply for storage paths. Pin a version in composer.json so an unexpected release does not break your upload pipeline.
What features does the bundle actually provide?
The package focuses on managing uploaded images and files through reusable media entities, storage handling and thumbnail support. It is positioned as a lightweight foundation for common content workflows rather than a full digital asset management suite. That makes it a reasonable starting point if you want simple upload and thumbnail behaviour you can extend yourself.
Which Symfony and PHP versions does oosaulenko/media-bundle support?
The overview does not state exact version constraints, so verify them in composer.json and the README before installing. Match the bundle's Symfony constraint against the framework version your application already runs. If you are on an older Symfony release or a very new PHP major, test the installation in a branch first rather than on a production checkout.
How does thumbnail generation work in this bundle?
Thumbnail support is listed as a core feature, alongside reusable media entities and storage handling. The overview does not say which image backend is used, so inspect the source for whether it relies on GD, Imagick or an external image-processing library. Confirm the thumbnail sizes and generation timing, since generating thumbnails synchronously on upload can slow down requests in a busy application.
Can I store media on S3 or a custom filesystem with oosaulenko/media-bundle?
The bundle provides storage handling for uploaded files, but the overview does not document which filesystem abstraction it uses. If it is built on a standard Symfony filesystem layer, wiring in S3 through Flysystem or a custom adapter is usually straightforward. Inspect the storage classes and configuration before committing, and consider a local adapter for development to keep iteration fast.
How should I test media uploads and thumbnails with this bundle?
Write functional tests that boot the Symfony kernel, simulate an upload through the test client, and assert that the media entity is persisted and the expected files exist. Point storage at a temporary directory or in-memory adapter so CI runs do not touch real buckets or leave orphaned files. Also test failure paths such as invalid MIME types and oversized files, because those are the cases that break in production.
Is oosaulenko/media-bundle actively maintained and safe for production?
The available context shows a single-maintainer project with limited public signals, so do your own due diligence before relying on it. Check the commit history, last release date, open issues and whether tests run in CI. For critical upload paths, consider forking the package into your own VCS or wrapping it behind an interface so you can swap it out later.
What are good alternatives for media management in a Laravel project?
For Laravel specifically, Spatie's Laravel Media Library is the most common choice, with Intervention Image handling conversions and resizing. Other options include smaller mediable-style packages and building a thin upload service around Laravel's filesystem and queues. Because oosaulenko/media-bundle is Symfony-oriented, a Laravel-native package will almost always be faster to ship.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
shitoudev/permissionmanager
johannesclimacus/laravel-tui
hocvt/seotools
vitalybaev/sypexgeo
amphibee/themosis-ignition
gito-me/fast-excel
frankyso/laravel-ipaymu
geolize-studio/laravel-chile
boomerangui/chat
jinas/dhivatar
store-doc/laravel-storage-driver
plus-it/laravel-translation-manager
diephp/perhaps
diephp/telegraph
osmaviation/spreadsheet
microsoft/fluentui-system-icons
mmccook/php-json-canonicalization-scheme
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console