- Can I use joos/open-tok-bundle in a Laravel application?
- No. joos/open-tok-bundle is a Symfony2 bundle with a Bundle class, DI extension, and service container wiring, not a Laravel package. It has no service provider, facade, or publishable Laravel config, and Laravel's container cannot consume it without a bridge. For Laravel, use the maintained vonage/client SDK directly behind your own service provider.
- How do I install joos/open-tok-bundle?
- In a legacy Symfony2 app you would require joos/open-tok-bundle via Composer, register the bundle in AppKernel, and configure your OpenTok API key and secret in the bundle config. There is no Laravel installation path because the package does not ship a service provider or config/video.php. Composer resolution may also fail on modern PHP due to pinned legacy Guzzle versions.
- Does joos/open-tok-bundle support Laravel 10 or Laravel 11?
- No. The bundle targets Symfony 2.x, which reached end of life in November 2018, and pins a legacy OpenTok SDK with old Guzzle 3.x/5.x dependencies. Modern Laravel applications run Guzzle 7 and PHP 8+, so Composer will either fail to resolve or force harmful downgrades. There is no Laravel 10 or 11 support.
- What PHP and Symfony versions does joos/open-tok-bundle require?
- The bundle was built in the Symfony 2.x era and targets PHP 5.6 through 7.x with the legacy TokBox OpenTok PHP SDK. That SDK depends on old Guzzle versions and does not align with modern PHP 8+ or current Symfony releases. Treat it as an end-of-life reference implementation, not a dependency for new applications.
- What is the Laravel alternative to joos/open-tok-bundle for OpenTok or Vonage Video?
- Use vonage/client directly and bind it in a Laravel service provider, for example a VideoServiceProvider, with configuration in config/video.php. You get the same session creation and token generation capability without a Symfony bridge or EOL framework in the dependency tree. This is the recommended path for new Laravel integrations.
- How do I generate OpenTok client tokens in Laravel?
- Install vonage/client, bind an OpenTok or Vonage Video client in a Laravel service provider, and call the SDK methods to create a session and generate a client token. Keep API key and secret in environment variables exposed through config/video.php. Do not install joos/open-tok-bundle for this, because it is Symfony2 wiring, not Laravel code.
- Is joos/open-tok-bundle maintained?
- No. The repository shows no recent activity, zero stars, and zero dependents, and it wraps an SDK for an API that has been rebranded under Vonage. Symfony 2.x has been EOL since 2018, so there are no security patches or maintainer SLA. An abandoned package is also a supply-chain concern if ownership changes.
- How should I test OpenTok or Vonage Video integration in Laravel?
- Wrap the vonage/client SDK behind your own interface and inject that interface into your application services. In unit tests, bind a mock implementation that returns predictable session IDs and tokens, and keep HTTP-level integration tests separate. This gives you mockable seams without relying on a Symfony bundle's container wiring.
- What are the production risks of adopting joos/open-tok-bundle?
- The main risks are an EOL Symfony 2.x framework, legacy Guzzle dependency conflicts with modern Laravel, and vendor drift from OpenTok to Vonage Video. Adopting it can force HTTP client downgrades that destabilize unrelated features such as payments, mail, and webhooks. It also lacks security review, activity, and a maintainer SLA.
- Should I migrate from joos/open-tok-bundle to vonage/client?
- Yes. Reimplement the bundle's roughly 100 lines of config and container wiring as a Laravel service provider and config file, then depend on vonage/client for session and token operations. Migrate credentials to environment variables with a rotation policy and plan for webhook handling separately. The bundle is useful only as a shape reference, not as installed code.