- What is p-sam/real-time-bundle used for?
- It is a PHP real-time bundle that lets your backend push live updates to connected clients over WebSockets or Server-Sent Events instead of relying on polling. It provides a publishing layer for broadcasting domain and custom events to real-time channels and topic-based subscribers. It works alongside existing PHP and Symfony applications and is designed to be lightweight.
- How do I install p-sam/real-time-bundle in a Laravel application?
- Install it with Composer using composer require p-sam/real-time-bundle, then wire its publishing layer into your application's service container. Because the package is built as a Symfony bundle rather than a Laravel-native package, Laravel projects may need manual integration instead of relying on package discovery. Confirm that your PHP and Symfony component versions meet the v1.3.0 minimums before installing.
- Does p-sam/real-time-bundle support Laravel 6, 7, and 8?
- The bundle is not Laravel-specific, but v1.3.0's PHP 7.2+ and Symfony 4.4/5.x baseline matches Laravel 6.x and later. The technical assessment positions it as compatible with Laravel 6, 7, and 8 environments. Laravel 5.x projects will not meet the new dependency floors without modernizing PHP and Symfony components first.
- What PHP and Symfony versions does p-sam/real-time-bundle v1.3.0 require?
- Version 1.3.0 requires PHP 7.2 or newer and Symfony 4.4 or newer. It explicitly drops support for PHP below 7.2 and Symfony below 4.4. The release is therefore breaking for older stacks and acts as a hard install guardrail.
- Can I use WebSockets or Server-Sent Events for live updates with this bundle?
- Yes, the bundle supports pushing live updates over WebSockets and Server-Sent Events. That lets you choose a transport for dashboards, notifications, or collaborative views without manual refreshes. The package overview describes it as event-driven rather than polling-based.
- How do I broadcast custom events to topic-based subscribers?
- Use the bundle's publishing layer to broadcast domain events or custom events to named real-time channels. Subscribers receive routed updates through topic-based subscriptions, so you can target specific views or user groups. The API is intended to keep wiring minimal from any service in your application.
- Do I need a heavy client-side library or frontend SDK?
- No heavy client library is required according to the package overview. The focus is on a simple server-side publishing layer that broadcasts events over WebSockets or Server-Sent Events. You should still validate how your chosen transport connects in the browser and whether your frontend needs minimal handling for incoming messages.
- What breaks if I upgrade to v1.3.0 on an older Laravel app?
- On PHP below 7.2 or Symfony below 4.4, Composer will likely fail to resolve dependencies for v1.3.0, and force-installing it can cause runtime errors. Pin the previous package version if you cannot upgrade immediately, then modernize PHP first, followed by Symfony or the Laravel version that bundles it. Treat v1.3.0 as a downstream dependency and upgrade the runtime and framework before adopting it.
- What are the alternatives to p-sam/real-time-bundle for Laravel real-time updates?
- The bundle is a lightweight option for server-side event broadcasting without a heavy client library. Laravel teams often compare it with Laravel's broadcasting system and hosted WebSocket services, but this package is Symfony-oriented and may require extra integration in Laravel. Evaluate alternatives on transport support, authentication, scaling, and how much Laravel-native tooling you need.
- Is p-sam/real-time-bundle actively maintained and production-ready?
- Version 1.3.0 signals active maintenance and a willingness to track upstream Symfony releases. The technical assessment found no documented support policy, LTS commitment, or confirmed security-fix process, so confirm those with the maintainer. Production readiness still depends on your transport, connection management, monitoring, and rollback plans; the compatibility release itself does not target performance.