- Can I use pulse00/ffmpeg-bundle in a Laravel application?
- No. pulse00/ffmpeg-bundle is a Symfony bundle that registers a container service and DI extension; it is not a Laravel package and will not auto-discover as a service provider. For Laravel, use php-ffmpeg/php-ffmpeg directly and wrap it in a thin service provider and config file.
- How do I install pulse00/ffmpeg-bundle?
- Install it with Composer using composer require pulse00/ffmpeg-bundle, then register the bundle in a Symfony application's kernel and configure the FFmpeg and FFprobe binary paths in YAML. It is not installed or configured through Laravel's provider or config system.
- Does pulse00/ffmpeg-bundle support Laravel 10 or Laravel 11?
- No. The package is built for Symfony 2.x/3.x and does not provide a Laravel service provider, facade, or package discovery. Laravel 10 and 11 need a framework-agnostic wrapper such as php-ffmpeg/php-ffmpeg plus your own integration code.
- What PHP version does pulse00/ffmpeg-bundle 0.6.0 support?
- Version 0.6.0 declares PHP 7 support, which in practice means early PHP 7.0/7.1-era compatibility, not PHP 7.4 or PHP 8. There is no evidence of a CI matrix or fixes for PHP 8 typed properties and deprecations, so assume it is not viable on modern PHP without a fork.
- What Symfony versions are compatible with pulse00/ffmpeg-bundle 0.6.0?
- Version 0.6.0 adds support for Symfony 3 alongside existing Symfony 2.x support. Symfony 3.4 reached end of maintenance in November 2021, so the release that makes the bundle usable for Symfony 3 also anchors it to an end-of-life framework branch.
- How do I configure the FFmpeg binary path in pulse00/ffmpeg-bundle?
- In a Symfony app you configure the bundle through YAML, setting the paths to the ffmpeg and ffprobe executables used by the underlying PHP-FFMpeg library. In Laravel you would instead publish a config file for your own wrapper and pass the binary paths into php-ffmpeg/php-ffmpeg.
- Do I need FFmpeg installed on the server to use pulse00/ffmpeg-bundle?
- Yes. The bundle and php-ffmpeg/php-ffmpeg are wrappers around system FFmpeg and FFprobe binaries, so the executables must be installed and reachable from the PHP process in every environment. Missing or mismatched FFmpeg builds are the most common cause of local-versus-production failures.
- What is the best Laravel alternative to pulse00/ffmpeg-bundle?
- For Laravel, use php-ffmpeg/php-ffmpeg directly and bind it in a custom service provider with a config file for binary paths and timeouts. That gives you the same thumbnail, metadata, filter, and conversion capabilities without depending on a Symfony bundle.
- Is pulse00/ffmpeg-bundle actively maintained and safe for production?
- It appears effectively community-maintained: version 0.6.0 was a compatibility bump with no active release cadence or support contract evident. For production, the bigger risks are the dead Symfony 3 branch, old PHP assumptions, transitive dependency drift in php-ffmpeg/php-ffmpeg, and unpatched security issues.
- How should I test and secure FFmpeg processing in a Laravel app?
- Mock or fake the FFmpeg wrapper in unit tests and run a small integration suite against a real binary in CI so codec and path issues surface early. Treat user-supplied filenames, formats, and filters as untrusted, validate and escape arguments, and avoid building shell command strings from request input to reduce command-injection and SSRF risk.