Weave Code
Core Bundle Laravel Package
os2display/core-bundle
Core bundle for the OS2display digital signage platform, providing shared domain models, services, and integration glue for screens, content, and scheduling. A foundational PHP/Symfony package for building and extending OS2display deployments.
Os2Display core
Frequently asked questions about Core Bundle
- Is os2display/core-bundle a Laravel package?
- No. os2display/core-bundle is a Symfony bundle for the OS2display digital signage platform, not a Laravel package, so it does not use Laravel package discovery or service providers. You cannot expect a standard Composer install to wire it into a Laravel app. For Laravel, treat OS2display as a separate Symfony service and integrate over HTTP or a message bus.
- Can I install os2display/core-bundle in a Laravel application?
- Composer may install the code, but it will not behave like a Laravel package because Laravel does not have Symfony's bundle and kernel-extension model. A direct dependency is low-feasibility; a co-deployed Symfony service is the practical route. Do not try to shim Symfony bundle loading into Laravel's service container.
- What Laravel versions does os2display/core-bundle support?
- Laravel version support is not applicable because this is not a Laravel package; it is a PHP/Symfony bundle for OS2display. You should check the bundle's supported Symfony and PHP version matrix instead. Laravel compatibility only applies through a service-boundary integration, not as an in-process dependency.
- What is os2display/core-bundle used for?
- It provides shared domain models and core services for OS2display digital signage, including screens, content, and scheduling. It acts as an integration layer so related OS2display packages can reuse common behavior and configuration. It is not a general-purpose library and likely expects sibling OS2display bundles at runtime.
- How do I install and configure os2display/core-bundle?
- Install it with Composer inside a Symfony application, register the bundle, and expect platform-specific configuration plus sibling bundles such as screen, media, template, and scheduling components. The repository is the source of truth for exact Symfony and PHP requirements. For Laravel projects, install it only in a separate Symfony service rather than the Laravel app itself.
- What changed in os2display/core-bundle 2.2.3?
- Release 2.2.3 adds a screen admin role and fixes an issue in the serialization listener. It is a patch-level release with no advertised migrations, deprecations, or public API removals. Confirm whether the new role is auto-provisioned or manually assigned and review the serialization diff for response payload changes.
- Does os2display/core-bundle work with digital signage screens and scheduling?
- Yes, its stated purpose covers shared models and services for screens, content, and scheduling in OS2display deployments. It is intended to be extended with custom signage features and reused across OS2display components. It is not a turnkey signage application on its own and depends on the wider OS2display bundle ecosystem.
- How should I integrate OS2display with Laravel?
- The recommended approach is to run OS2display as a separate Symfony-based signage service and integrate from Laravel through an HTTP API and/or a shared message bus. This preserves your Laravel architecture and avoids forcing Symfony bundle semantics into Laravel. If you truly need to embed signage domain logic, adopt Symfony for that bounded context instead.
- What are the production risks of using os2display/core-bundle with Laravel?
- The dominant risk is stack mismatch: this is a Symfony bundle, so direct Laravel use is high risk. Also assess the authorization matrix behind the new screen admin role and whether the serialization listener fix changes response body shape or field ordering. Release hygiene looks low risk because 2.2.3 is a patch with no breaking-change markers, but you still need to understand authentication, persistence, and event or queue assumptions.
- Are there alternatives to os2display/core-bundle for Laravel digital signage?
- For a Laravel-native solution, look for Laravel packages or build the signage domain directly in Laravel; OS2display is Symfony-based and not a drop-in alternative for Laravel. If you specifically need the OS2display platform, use it as a Symfony service and integrate over APIs or queues. Evaluate sibling bundle requirements and release cadence before committing.
Weaver
How can I help you explore Laravel packages today?