- Is teltek/pumukit-blackboard-bundle a Laravel package?
- No. It is a Symfony bundle built as a plugin for a running PuMuKIT video platform instance, not a Laravel package. It ships no service provider, facade, or Laravel-style config publishing, and its controllers are bound to Symfony's HTTP kernel, DI container, and routing. You cannot drop it into a Laravel application.
- Can I install teltek/pumukit-blackboard-bundle with Composer?
- Composer can resolve and install it in principle, but it only functions inside a PuMuKIT deployment at a compatible release. You also need a matching Symfony major version, MongoDB ODM, PuMuKIT core services, and a reachable Blackboard tenant with the right API credentials. Standalone or outside PuMuKIT it has essentially no reusable value.
- Which Laravel versions does this package support?
- None. The package is Symfony-only and publishes no Laravel version matrix or compatibility table. Treat the 'Laravel/PHP package' framing as inaccurate and do not attempt to install it in a Laravel app. Use a native adapter instead.
- What are the requirements to run teltek/pumukit-blackboard-bundle?
- You need a working PuMuKIT instance at a compatible release, a matching Symfony major version, MongoDB ODM, and PuMuKIT core domain services present. You also need a reachable Blackboard tenant with correct API credentials, the matching Blackboard-side integration, and network or security changes to expose an ingest endpoint. None of these preconditions are documented in a verifiable way from the repository alone.
- What does this bundle actually do?
- It adds an import and ingest API surface that lets a Blackboard LMS instance push or expose course-associated video content into the PuMuKIT media catalogue. The code is mostly wiring: DI configuration, routing, controllers, and a Blackboard-facing client and service against PuMuKIT core domain objects. It is narrow, prescriptive, and only meaningful inside PuMuKIT.
- Which Blackboard integration does it implement: REST API, LTI 1.3, or legacy Building Block?
- This is not documented in the repository, so you must confirm it by reading the code or asking the vendor. The Blackboard integration contract, including auth model, payload schema, pagination, and idempotency, is undocumented here. You cannot size the work until that contract is clear.
- Is the ingest endpoint secure enough for production?
- There is no documented threat model, and a loosely authenticated or unauthenticated content ingest endpoint needs review before production. Confirm the authentication and authorization model, how tenant and course mappings are resolved, and whether the import is idempotent on partial failure or duplicate delivery. Do a security review first.
- Is teltek/pumukit-blackboard-bundle actively maintained?
- There are zero stars, zero dependents, and no community or downstream validation, so assume single-vendor maintenance with no obligation to respond to issues. Tight coupling to PuMuKIT internals means each PuMuKIT upgrade is a potential breaking change. Confirm the release cadence, supported PuMuKIT releases, and whether commercial support is required.
- What should I use instead in a Laravel application for Blackboard video integration?
- Do not install this bundle in Laravel. Treat the repository as a reference implementation for the Blackboard ingest contract and re-implement the adapter natively: a Blackboard API client, a normalizing mapper into your media model, and a queue-backed ingest job. This is greenfield integration, not a migration.
- Does the bundle handle transcoding and partial failures?
- It is unclear from the repository whether it hands media off to PuMuKIT's transcoding pipeline or assumes pre-transcoded input. It is also unclear whether the import is idempotent and what happens on partial failure, retry, or duplicate delivery. Ask the vendor these questions before relying on it in production.