- Can I use gos/web-socket-bundle directly in a Laravel application?
- Not directly. gos/web-socket-bundle is a Symfony bundle built around a Bundle subclass, a DependencyInjection extension, compiler passes, and kernel event subscribers, and it ships no Laravel service provider, facade, publishable config, or Artisan command. You can only use it in Laravel via an out-of-process sidecar Symfony service or by forking and re-hosting its Ratchet and WAMP pieces behind a Laravel service provider.
- Does gos/web-socket-bundle support Laravel 11 and Laravel 12?
- There is no Laravel support in the package. Laravel 11 and 12 pin Symfony 7 components, while the latest gos/web-socket-bundle release, v3.15.0, is a deprecation fix scoped to Symfony 6.1 command configuration. That does not confirm Symfony 7 compatibility, so treat it as unverified and high-risk for a Laravel 11 or 12 dependency chain.
- How do I install gos/web-socket-bundle with Composer?
- In a Symfony application you install it with composer require gos/web-socket-bundle, register the bundle in your kernel, and configure it through YAML. In Laravel there is no package auto-discovery path, no service provider, and no config file to publish, so composer require alone will not wire it into the framework. A Laravel setup requires either a separate Symfony service or a custom fork.
- What is the difference between gos/web-socket-bundle and Laravel Reverb?
- Laravel Reverb is first-party, speaks the Pusher protocol, and integrates with Laravel Echo and Laravel's broadcasting stack. gos/web-socket-bundle is a Symfony bundle that runs a Ratchet server with WAMP-style topic subscriptions, RPC, periodic timers, PubSub, and an Autobahn.JS client. Its Autobahn client does not interoperate with Laravel Echo, so Reverb is the better fit unless you specifically need WAMP pub/sub plus RPC over one connection.
- Can I run gos/web-socket-bundle as a sidecar alongside my Laravel app?
- Yes. You can deploy the bundle as a standalone Symfony microservice in its own container, let it talk WAMP to browsers, and bridge events to Laravel over Redis pub/sub or an internal HTTP broadcast endpoint. That keeps Laravel clean, but it adds a second framework, a second deploy pipeline, and a second on-call surface.
- Does gos/web-socket-bundle work with Laravel Octane or Swoole?
- It is a poor fit. The bundle runs on Ratchet and ReactPHP's event loop, which is a blocking concurrency model that sits badly beside Octane, Swoole, or RoadRunner. Running both in one deploy target gives you two concurrency models and makes singleton and database-connection leakage a live class of bug.
- How do I authenticate WebSocket connections for Laravel users with gos/web-socket-bundle?
- The bundle integrates with Symfony's security layer, not Laravel's guard or session, so there is no built-in path for Laravel users. A sidecar setup needs a token or session bridge, plus a plan for refreshing credentials on a long-lived connection. You would also need a custom connection handler to map your Laravel identity model onto the bundle's session handling.
- Is gos/web-socket-bundle actively maintained and production-ready?
- v3.15.0 is the first release since 2022-09-20 and is a single deprecation fix for Symfony 6.1 command configuration. It shows the maintainer is reachable and the package is not formally abandoned, but one maintenance commit after roughly two years does not establish release cadence. With 609 stars, zero dependents in this dataset, and a bus factor of one, adoption is thin and technical risk is high.
- Does gos/web-socket-bundle support RPC and topic-based messaging?
- Yes. It provides topic-based publish/subscribe with configurable handlers and subscribers, RPC, periodic timers, PubSub for background events, and session-aware connection management on top of Ratchet and WAMP. Those features are real, but they are exposed through Symfony container wiring and kernel events rather than Laravel service providers. If plain channel pub/sub is enough, Laravel-native transports are simpler and better supported.
- What are the best alternatives to gos/web-socket-bundle for Laravel real-time features?
- For most Laravel apps, use Laravel Reverb, which is first-party and works with Laravel Echo and the Pusher protocol, or Soketi if you want a self-hosted Pusher-compatible server. You can also run Ratchet directly with cboden/ratchet behind a custom Artisan command if you want lower-level control. Choose gos/web-socket-bundle only if you specifically need WAMP-style pub/sub plus RPC and are willing to run it as a Symfony service or maintain a fork.