Weave Code
Campaign Bundle Laravel Package
os2display/campaign-bundle
The os2display/campaign-bundle is a PHP package for the OS2Display digital signage platform that adds campaign management features, helping organize, schedule, and display campaign content across screens in OS2Display-based applications.
OS2Display Campaign Bundle adds campaign management to the OS2Display digital signage platform. It lets you group screens and channels into campaigns, so shared content is published and scheduled across many displays at once instead of being configured per screen. The bundle plugs into the wider OS2Display ecosystem and is wired up through standard Symfony service configuration.
- Create campaigns spanning multiple screens and channels
- Schedule content with start and end times
- Bind shared slides to campaign-wide content
- Integrates with the OS2Display screen and content bundles
- Configured via Symfony DI and bundle services
Frequently asked questions about Campaign Bundle
- Can I use os2display/campaign-bundle in a Laravel application?
- It is built as a Symfony bundle for OS2display digital signage, not a Laravel package, so there is no documented Laravel service provider or auto-discovery path. A Laravel team could only consume it after confirming it works standalone or through Symfony integration, and the first-pass TPM assessment flags stack fit as unverified. Treat it as a Symfony component until proven otherwise.
- How do I install os2display/campaign-bundle with Composer?
- Use composer require os2display/campaign-bundle, and pin 2.1.0 exactly for a first introduction rather than a caret constraint. Install on a non-production branch, then publish config and assets and diff the published output against the repository. Auto-discovery and publishable tags are assumed but unverified for this bundle.
- What does os2display/campaign-bundle actually do?
- It extends OS2display with campaign management: create, schedule, and organize content campaigns, assign them to screens or channels, and control playback timing. Campaigns force screens to show only the selected content for a given period, then return to normal content afterward. It sits in the rendering and asset-composition tier rather than the domain tier.
- Is the campaign icon change in 2.1.0 a breaking change?
- The release notes label the campaign icon change as cosmetic, but it is a contract change for anything referencing the old asset by name or path. No deprecation or migration note ships with it, so check whether the previous icon is still present, aliased, or removed outright. Inventory Blade, CSS, asset manifests, and CDN cache keys before upgrading.
- What is screen-bundle support in campaign-bundle 2.1.0?
- Release notes say support for screen-bundle was added, which implies a new bundle or screen registration path layered onto an existing abstraction. It is likely additive and wired through config rather than a restructure, but the package's exact vocabulary for a screen-bundle is not defined in the notes. Confirm whether it alters existing bundle resolution and whether tests cover that path.
- Does campaign-bundle ship front-end assets and templates?
- The 2.1.0 notes read like it does: an icon change is presentation-layer and asset work, suggesting the bundle ships front-end assets and possibly templates. That changes ownership, because you inherit asset publishing and cache-busting concerns. Publish assets and diff them against the repository to see exactly what the package writes.
- What are the PHP and Laravel version requirements for campaign-bundle?
- Laravel version support is not stated, and the package is a Symfony bundle, so read the actual constraints directly from its composer.json rather than inferring them. Check PHP constraints, Symfony component constraints, and transitive package count before scoping. Standard Laravel package consumption is assumed but unverified.
- How do I pilot os2display/campaign-bundle safely?
- Pin 2.1.0 exactly, install on a non-production branch, publish config and assets, and register one low-traffic screen bundle as a pilot. Do not migrate existing bundles, and diff rendered output pre- and post-install. Confirm the package is not a wrapper around an external SaaS before scoping the work.
- Is os2display/campaign-bundle actively maintained and tested?
- The evaluation notes a thin release history: two bullet points with no PR links, changelog detail, or semver rationale, so release cadence and issue responsiveness are unknown. Ask who maintains it, whether 2.x is the supported line, and whether CI is green on the tagged commit. Check whether tests cover the new screen-bundle path.
- Should other packages depend on os2display/campaign-bundle?
- Probably not: it looks like a leaf dependency in the rendering and asset-composition tier, consumable by controllers, Blade components, or API resources rather than infrastructure. Confirm that classification before treating it as a shared dependency. If you hand-roll screen or bundle composition today, adoption is a refactor, not an install.
Weaver
How can I help you explore Laravel packages today?