Weave Code
Screen Bundle Laravel Package
os2display/screen-bundle
Symfony bundle from the OS2display digital signage platform that adds screen management to your application, with entities, API endpoints, and admin integration for registering, configuring, and delivering content to displays.
Bundle that integrates the screen code into the administration.
Frequently asked questions about Screen Bundle
- Is os2display/screen-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle, not a Laravel package. It is part of the OS2display digital signage platform and is built around Symfony's kernel, dependency injection container, event dispatcher, and typically Doctrine persistence. Composer can install it, but Laravel's service container and Eloquent will not natively understand its Symfony-specific contracts. Treat it as a Symfony component your Laravel application would consume, not an in-process library.
- How do I install os2display/screen-bundle?
- Install it with composer require os2display/screen-bundle inside a Symfony application, then register the bundle in your kernel and configure its routes and Doctrine mappings. Verify the PHP and Symfony version constraints declared in the package composer.json before installing. Pin an explicit version such as 1.1.7 rather than floating the constraint, and review the lockfile diff. There is no Artisan installer or Laravel package auto-discovery support.
- Can I use os2display/screen-bundle inside a Laravel application?
- Not as an in-process library without significant effort. The bundle assumes Symfony's container, event dispatcher, and Doctrine, so pulling it into Laravel creates a permanent impedance mismatch at the container, ORM, and configuration layers. The practical pattern is a sidecar Symfony service that owns screens, channels, slides, and schedule evaluation while Laravel consumes a stable HTTP or queue contract. Scope a timeboxed spike before committing to either approach.
- What PHP and Symfony versions does os2display/screen-bundle 1.1.7 require?
- The 1.1.7 changelog does not state version constraints, so you must read the composer.json in the tagged release rather than assume. Check the declared PHP range and Symfony component constraints against your host before updating. Also confirm the patch does not raise minimum versions or introduce hidden transitive dependency bumps. Pin the version explicitly and commit the lockfile diff for review.
- What changed in os2display/screen-bundle 1.1.7 and is it a safe upgrade?
- Release 1.1.7 is a patch whose only stated change is a fix for channel scheduling via PR #14, so it is semver-compatible with low blast radius and no signalled breaking changes. The caveat is that scheduling is the core correctness surface of a signage product, and a one-line changelog entry is thin evidence for a change to that subsystem. Read PR #14 and the linked issue, confirm whether schema drift is implied, and verify constraint ranges before merging.
- What was the channel scheduling bug fixed in os2display/screen-bundle 1.1.7?
- The changelog only says it fixed an issue with channel scheduling and does not document the root cause, affected versions, or whether content was skipped, duplicated, or shown outside its window. Timezone and DST handling and overlapping channel windows are the usual suspects and should be assumed until disproven. Review PR #14 and the linked issue directly to confirm the failure mode. If you rely on scheduling, add your own regression coverage.
- Does os2display/screen-bundle require Doctrine?
- The bundle is built around Symfony and typically Doctrine persistence for its screen, channel, and slide entities. Confirm the exact mapping and migration state in the release you install, since a scheduling fix may or may not imply schema changes. Plan and run migrations in the Symfony host rather than inside the Laravel application. If you go the sidecar route, isolate the database so Laravel never writes directly to Doctrine-managed tables.
- How should a Laravel app get screen and channel data from os2display/screen-bundle?
- Run the bundle in its native Symfony host and expose a content and schedule API, then have Laravel consume that contract over HTTP or a shared queue. Keep screens, channels, slides, and schedule evaluation in the Symfony service, and let Laravel own users, tenancy, billing, and presentation. This confines Symfony-specific dependencies to one runtime and gives you a stable seam to version. Avoid reaching into Doctrine tables directly from Eloquent.
- Is there a regression test for the scheduling fix in os2display/screen-bundle?
- The available evaluation material does not confirm a public regression test for the 1.1.7 scheduling change, so treat that as unverified. Check the pull request and CI configuration for coverage of timezone and DST cases, which are the most common sources of scheduling defects. If none exists, write your own tests around window boundaries and overlapping channels. Do this before relying on the fix in production.
- Is os2display/screen-bundle actively maintained and what are the alternatives?
- Release cadence, issue-triage responsiveness, commercial backing, SLA, and security-disclosure process are not established in the evaluation notes and should be verified against the repository over the last 12 months. If the project proves purely community-maintained, plan for higher operational ownership and slower fixes. Alternatives depend on your stack: a maintained Symfony signage bundle if you stay on Symfony, or a build-versus-buy review of commercial digital signage platforms if you require an SLA.
Weaver
How can I help you explore Laravel packages today?