- Is mztx/shinage-player-bundle a Laravel package?
- No. It is a Symfony bundle: it ships a Bundle class registered in the kernel, a DependencyInjection extension for configuration, service definitions, and Twig templates. Laravel exposes none of those extension points, so there is no service provider, facade, or config publishing to hook into. Treat it as a Symfony artifact, not a Composer package you can drop into a Laravel app.
- Can I install mztx/shinage-player-bundle in a Laravel app with Composer?
- Composer may download the files, but installation is not integration. Laravel package auto-discovery will not find a Symfony bundle class, and there is no config file to publish or merge. Without a Symfony kernel and container, the player route and services are never wired up. Plan on extraction rather than installation.
- Does this package support Laravel 10, Laravel 11, or Laravel 12?
- It supports no Laravel version, because it targets Symfony's bundle system rather than Laravel's package contracts. The mismatch is at the framework-primitive level, not the API level. If you need a Laravel-native signage player, this is not it.
- How do you install and configure the Shinage player in a Symfony application?
- In Symfony you register the bundle in the kernel or bundles.php, configure services through standard Symfony service configuration, and use the bundled player route and Twig templates. Playlists are then loaded from a Shinage backend and looped full-screen. None of that wiring translates to a Laravel application without a rewrite.
- What is the best way to use the Shinage player frontend in a Laravel project?
- Extract the player surface only: pull the Twig templates and static assets, reimplement the markup as a Blade component with an equivalent data contract, and feed it from Laravel. Skip the Symfony runtime, Doctrine repositories, and container configuration entirely. This extraction path is the only one where the effort is plausibly smaller than writing the player from scratch.
- Is mztx/shinage-player-bundle maintained and safe to use in production?
- The project is archived with no maintainer, roughly 1 star, and zero dependents. There is no security response, no issue triage, and no guarantee of PHP 8.x or Symfony 5 through 7 compatibility. Whatever you vendor becomes yours permanently on day one, so treat any adoption as a fork.
- What are the alternatives to this bundle for digital signage in a Laravel application?
- The realistic options are extracting the front-end into a Blade component, reimplementing the playlist and scheduling model behind Laravel interfaces backed by Eloquent, or deploying the player as a standalone static artifact served from its own origin. The standalone route is often best for signage, because player release cadence should not be coupled to application release cadence. Bridging Symfony DI into Laravel is not a viable alternative.
- How do I test a Shinage player extracted into Laravel?
- You cannot meaningfully test the bundle inside Laravel because it will not boot without a Symfony kernel. Instead, treat the source as a reference read, then test your Blade component with your own fixtures for playlist payloads and media types. Add manual checks for Chromium autoplay policy, codec support on kiosk hardware, and long-uptime memory behavior before any screen goes live.
- What license does mztx/shinage-player-bundle use, and can I copy its templates and assets?
- The license is unverified in the available assessment, so copying any file is a distribution event with unknown terms. Confirm the license and whether partial extraction of templates and assets falls within it before vendoring a single file. Do this before the spike, not after.
- Will mztx/shinage-player-bundle install on PHP 8.2 or modern Symfony versions?
- Expect PHP 7.x-era composer.json constraints, possibly the abandoned symfony/symfony meta-package, and transitive dependencies that will not resolve on a modern runtime. Even as a reference, the package may not install anywhere, which limits your evaluation to reading the source. Check composer constraints first if you need to know whether a local install is even possible.