Weave Code
Vimeo Bundle Laravel Package
os2display/vimeo-bundle
A Symfony bundle that adds Vimeo video support to OS2Display, helping digital signage setups embed and manage Vimeo content in screens and slides.
Adds an os2display template for displaying Vimeo videos
Frequently asked questions about Vimeo Bundle
- Can I use os2display/vimeo-bundle in a Laravel application?
- Not directly. It is a Symfony bundle built for the OS2Display digital signage platform, so it ships a DI extension, Resources/config and bundle registration rather than a Laravel ServiceProvider or Facade. The pragmatic route is to require it for its Vimeo domain logic and expose it through a thin first-party adapter in your own namespace. That keeps any future upstream rename or abandonment to a one-file change.
- How do I install os2display/vimeo-bundle with Composer?
- Run composer require os2display/vimeo-bundle, then read the package composer.json to establish the actual constraint set, because the release notes do not document minimum PHP or Symfony versions. If 2.0.0 also renamed the Composer package name, confirm whether the old name is abandoned or aliased before you rely on it. In a Laravel app you should not register the bundle through bundles.php; wire only the pieces you need in your own ServiceProvider.
- Does os2display/vimeo-bundle support Laravel package auto-discovery?
- There is no evidence of it. The package is named as a Symfony Bundle and the only documented change in 2.0.0 is a rename to Os2DisplayVimeoBundle, with nothing about an extra.laravel block, publishable config or a ServiceProvider. Expect to register config and services manually, and verify against the package composer.json rather than assuming discovery works.
- What breaks when upgrading to 2.0.0 of the Vimeo bundle?
- Version 2.0.0 is a major bump whose only documented change is the rename to Os2DisplayVimeoBundle. A rename of that kind typically cascades into the PSR-4 root namespace and every FQCN, service IDs and container aliases, config keys, Twig template paths and possibly Doctrine entity names. There is no changelog, diff or upgrade guide in the release notes, so the blast radius is unverified rather than zero. Grep for the old namespace and service IDs before bumping the dependency.
- Is this a general purpose Vimeo SDK or a digital signage slide type?
- It is a screen and media-type integration for OS2Display. It adds a Vimeo slide type with configurable video and playlist selection, plus preview and playback for scheduled screens, rather than exposing a broad Vimeo API client. If you need general Vimeo API coverage in Laravel, a plain Vimeo PHP SDK is a better starting point. This bundle is worth reusing mainly for embed and display behaviour.
- How should I configure Vimeo credentials in a Laravel app using this bundle?
- Do not rely on bundle-level config for secrets. Put the token in config/vimeo.php sourced from environment variables, read it through Laravel's config repository, and bind an authenticated client as a singleton in a ServiceProvider. The release notes do not state which auth model the bundle expects, so confirm whether it needs a client token, access token or OAuth flow before wiring anything. Plan for rotation and keep tokens out of version control.
- Which PHP, Symfony and Laravel versions does os2display/vimeo-bundle support?
- That is not established by the available information. The technical assessment explicitly flags the absence of documented PHP and Laravel version constraints, plus no visible release cadence. Read composer.json in the 2.0.0 tag and map its constraints against your runtime before committing. Do not assume Laravel compatibility just because it installs through Composer.
- Is os2display/vimeo-bundle tested and actively maintained?
- There is no visible evidence of tests, CI or a regular release cadence, and the project appears to have single-vendor, single-project provenance. The 2.0.0 release is one line of release notes on a major version bump, which is thin material for a risk assessment. If you adopt it, own the glue code and keep either a maintained fork or a direct Vimeo SDK as a fallback.
- What are the alternatives to this bundle for Vimeo in Laravel?
- If you only need playback, you may not need a package at all: Vimeo's iframe embed plus your own slide model is often enough. If you need API access to videos, playlists or uploads, use a plain Vimeo PHP SDK and wrap it in a small Laravel service, which avoids Symfony bundle semantics entirely. Check whether a maintained fork of os2display/vimeo-bundle exists before adopting the original.
- How should I handle Vimeo API rate limits and uploads with this bundle?
- The release notes say nothing about API version, rate-limit handling, or whether the package covers uploads rather than embed and display only. Embed-only usage is low risk, while upload and tus-style flows are materially more complex and need retry and backoff logic that you own. Put Laravel's HTTP client or a queued job in front of any write operations instead of relying on bundle behaviour, and keep the adapter in your own namespace.
Weaver
How can I help you explore Laravel packages today?