Weave Code
Laravel Ratchet Laravel Package
askedio/laravel-ratchet
Laravel Ratchet integrates the Ratchet WebSocket library into Laravel, making it easy to run real-time WebSocket servers alongside your app. Configure and start a server with Artisan, handle connections and messages, and push live updates without extra infrastructure.
A Ratchet Server built for Laravel
Frequently asked questions about Laravel Ratchet
- Does askedio/laravel-ratchet work with Laravel 10 or Laravel 11?
- In practice, no. The package's last release was in 2018, so it is constrained to the older Illuminate, Symfony, and PHP versions of the Laravel 5.x/6.x era, and it is very likely to fail on PHP 8.2+ and Laravel 10/11. A time-boxed compatibility spike in a container is mandatory before you commit to it. For modern stacks, evaluate Laravel Reverb, Soketi, Pusher, or a standalone Ratchet/ReactPHP service instead.
- How do I install askedio/laravel-ratchet?
- Install the package with Composer, publish its configuration file, and then start the WebSocket server using the Artisan serve command the package provides. Because the project is unmaintained, pin exact Composer versions for PHP, Laravel, Illuminate, Symfony, and Ratchet so an unrelated dependency update does not silently break the install. Verify required PHP extensions and test the install inside a container that matches production.
- Which PHP and Laravel versions does askedio/laravel-ratchet support?
- The package targets the Laravel 5.x/6.x era on PHP 7.x, matching its 2018 release timeframe. It is not a good fit for Laravel 10 or 11 on PHP 8.2+, where compatibility is expected to be low. Build a version matrix covering PHP, Laravel, Illuminate, Symfony, and Ratchet before integrating, and treat any newer combination as unsupported until proven otherwise.
- What is askedio/laravel-ratchet actually used for?
- It is a thin Laravel integration around the Ratchet WebSocket library that lets you run a long-running PHP WebSocket process alongside your app. Typical use cases are server-push features such as notifications, chat, live dashboards, and presence indicators, without adding extra infrastructure. It suits monolithic or small-service Laravel applications that can tolerate a self-hosted, single-process WebSocket server.
- How do I run the Ratchet WebSocket server with Artisan?
- After publishing the config, you start the server with the package's Artisan command and keep it alive under a process manager like Supervisor. Do not run it inside the normal web request lifecycle, because it is a long-running process. Add health checks and reconnect logic on the client, and plan TLS termination and proxy headers at the edge.
- How do I authenticate WebSocket connections with Laravel in this package?
- Expect to write custom authentication work, since session, token, and SSO handshakes are not handled out of the box in a modern, well-supported way. Decide up front whether WebSocket auth is tied to Laravel sessions, API tokens, or SSO, and validate the handshake behavior early in your spike. Also confirm how your reverse proxy forwards headers so authentication does not break behind TLS termination.
- Can askedio/laravel-ratchet scale across multiple servers?
- Not by default. The default model is a single long-running PHP process, which creates single-process bottlenecks and sticky-session concerns behind a load balancer. Horizontal scaling would require sticky sessions plus a pub/sub layer such as Redis, and you should not assume the package provides that. For strategic real-time platforms needing durable messaging or SLAs, use Reverb, Soketi, Pusher, or a dedicated service instead.
- Is askedio/laravel-ratchet still maintained?
- No, it is effectively unmaintained, with no release since 2018 and a small community footprint. Dependency updates, security patches, and PHP or Laravel upgrades will likely require forking or replacing the package, so budget for periodic compatibility work. Internal ownership must cover deployment, TLS, authentication, monitoring, and incident response because there is no vendor support.
- What are the best alternatives to askedio/laravel-ratchet?
- For modern Laravel applications, the usual choices are Laravel Reverb, Soketi, Pusher, or running your own Ratchet/ReactPHP service outside the framework integration. You can also keep Laravel broadcasting events and Laravel Echo on the client so the backend transport stays swappable. Designing behind that abstraction lets you migrate away from this package without rewriting product features.
- How do I move off askedio/laravel-ratchet later without rewriting features?
- Treat the package as an implementation detail behind Laravel broadcasting events and a narrow internal interface, and avoid coupling business logic to its server classes. Keep channel names, event payloads, and client behavior compatible with Laravel Echo so a later swap to Reverb, Soketi, or Pusher is mostly a transport change. Sequencing matters: prove auth and one event flow end to end, containerize and supervise the process, add monitoring, load-test concurrency, then pilot on a non-critical feature before a go/no-go decision.
Weaver
How can I help you explore Laravel packages today?