- What is teltek/pmk2-paella-player-bundle?
- It is a Symfony bundle that integrates the Paella Player HTML5 video player into PMK2 and Pumukit applications. It provides the bundle wiring and configuration needed to embed responsive, accessible media playback. It is not a Laravel package and is not designed for Laravel's service container, routing, or Blade templating.
- Does teltek/pmk2-paella-player-bundle work with Laravel?
- No, not directly. The package is built for Symfony and Pumukit and likely depends on Symfony service container conventions, Twig templates, routing, and Pumukit domain models. Laravel's container, Blade, and package discovery do not map to Symfony bundles, so adopting it as a Composer dependency in Laravel is not recommended.
- How do I install teltek/pmk2-paella-player-bundle?
- In a Symfony or Pumukit application you would normally require it via Composer and register the bundle. However, the last release was dated 2019-03-20, so verify PHP and Symfony compatibility before attempting installation. For Laravel, do not install it; use upstream Paella Player assets instead.
- Which Laravel versions are supported by teltek/pmk2-paella-player-bundle?
- None officially. The package is a Symfony bundle for Pumukit and does not declare Laravel support. Expect incompatibility with modern Laravel and PHP 8.1 or 8.2 runtimes because its 2019 release likely targets older Symfony and PHP versions.
- What PHP and Symfony versions does teltek/pmk2-paella-player-bundle require?
- The exact constraints are not detailed in the provided context, but the 2019 release date suggests older PHP and Symfony version targets. Validate Composer resolution in an isolated branch before any reuse. Do not assume compatibility with current Symfony or Laravel stacks.
- Is teltek/pmk2-paella-player-bundle actively maintained?
- No active maintenance is evident. It has 1 star, 0 dependents, and a last release dated 2019-03-20. That indicates negligible community adoption and a high risk of outdated dependencies and unpatched security issues.
- What is a good Laravel alternative for Paella Player integration?
- Integrate Paella directly as front-end JavaScript and CSS through Vite or copied static assets. Build Laravel-owned playback endpoints for manifests, captions, and authorization, and use a Blade, Inertia, or Livewire wrapper. Use the bundle only as a short-lived reference for assets and configuration patterns if licensing permits.
- How should I integrate Paella Player into a Laravel app?
- Use a Laravel-native wrapper: a Vite asset pipeline, a Blade, Inertia, or Livewire component, a playback token endpoint, and a media URL policy. Map any old bundle configuration to Laravel config and environment variables. Replace Pumukit-specific metadata calls with Laravel services or a thin sidecar API, test token issuance and manifest loading, and roll out behind a feature flag with a fallback player.
- Can I use Pumukit APIs from Laravel with this bundle?
- Not directly, because the bundle expects Symfony and Pumukit runtime services. If Pumukit APIs are mandatory, isolate them behind a sidecar service and expose a narrow playback contract to Laravel. Keep Symfony routes, Twig helpers, and Pumukit services out of the Laravel codebase.
- What are the production and security risks of using teltek/pmk2-paella-player-bundle?
- The risk is high because the package is unmaintained since 2019, likely targets older PHP and Symfony versions, and may bundle an outdated Paella Player version. Browser, codec, subtitle, DRM, and accessibility behavior are unknown. Verify licensing and transitive dependency posture before any reuse, and prefer a maintained Paella integration for production.