Weave Code
Ably Php Laravel Package
ably/ably-php
Official Ably Pub/Sub PHP SDK for realtime messaging, message history, presence, and push notifications. Install via Composer, then publish and subscribe using REST or realtime clients. Includes Laravel integration options.
Ably Pub/Sub SDK for servers (PHP). Construct clients with Ably\PubSub\Server::createHttpClient().
Frequently asked questions about Ably Php
- What is ably/ably-php used for in a Laravel application?
- It is a framework-agnostic REST client for Ably Pub/Sub. In Laravel it fits server-side publishing, message history retrieval, presence queries, token-request generation, channel status, and push admin operations. It is not a server-side realtime subscription SDK, so browser and mobile clients should connect directly to Ably with the appropriate client SDKs.
- How do I install and configure ably/ably-php in Laravel?
- Install it with composer require ably/ably-php. The raw SDK does not include a Laravel ServiceProvider or facade, so a typical integration is a small config/ably.php file, a singleton binding, and a publishing service wrapper around the AblyRest client. If you want Laravel DI and configuration sugar, Ably points Laravel teams to the separate ably-php-laravel package.
- Does ably/ably-php support realtime subscriptions or WebSockets?
- No, ably/ably-php is explicitly REST-only. It has no WebSocket connection lifecycle, no server-side subscription loop, and no native event listener. Anything requiring long-lived realtime ingress should use client SDKs directly, or a Reactor, webhook, queue, or MQTT adapter pattern for server-side consumption.
- Should I use an Ably API key or token authentication with Laravel?
- Use the raw API key only on the server side and never expose it to browsers or mobile clients. For anything client-facing, use Ably token authentication via TokenRequest or createTokenRequest so clients receive scoped, expiring credentials. The SDK exposes both models, but token auth should be the default security posture for client access.
- Which PHP and Laravel versions are supported by ably/ably-php?
- Modern releases of the SDK support PHP 8.2, 8.3, and 8.4, but the raw package is framework-agnostic and does not itself provide Laravel version integration. Laravel compatibility should be checked against the wrapper you choose, such as ably-php-laravel, and against Composer constraints on Packagist. Pin versions and review the changelog before upgrading.
- Is ably/ably-php suitable for production message publishing and retries?
- Yes, it is designed for server-side REST publishing and supports idempotent publishing, batch publish, host fallback, MsgPack, and protocol 2.0 in modern versions. You should still exercise idempotency, retry behavior, fallback-host handling, rate limits, and partial batch failures in staging because changelog history shows regressions in this area. Pin versions and track releases before production rollout.
- What are alternatives to ably/ably-php for Laravel realtime features?
- For Laravel-native event broadcasting, use the official ably/laravel-broadcaster instead of the raw REST SDK. For Laravel dependency injection, configuration, and facade-style access, use ably-php-laravel. The raw SDK remains the right choice for infrastructure-level REST operations when you want minimal framework coupling.
- How do I test Ably publishing in Laravel without hitting the real API?
- The raw SDK does not document Laravel testing helpers, so wrap publishing behind a small application service interface and mock or fake that wrapper in unit tests. Keep separate integration tests against a staging Ably app for publish, retry, idempotency, fallback-host, and partial batch failure behavior. This isolates Laravel tests from network calls while still exercising Ably-specific edge cases.
- What features does ably/ably-php support beyond basic pub/sub?
- It supports REST publishing, message history, presence queries, token-request generation, channel status, push notifications and push admin operations, batch publish, idempotent publishing, MsgPack, and host fallback. It does not provide server-side realtime subscription or a native event listener. For Laravel broadcasting specifically, use ably/laravel-broadcaster.
- Is ably/ably-php maintained and safe to adopt despite low stars?
- It is officially maintained by Ably, uses the Apache-2.0 license, and has recent releases, which mitigates abandonment risk more than the low star count suggests. Community adoption signal is weak at 61 stars and zero listed dependents, so expect limited community troubleshooting and rely on vendor docs and support. Also note that PHP SDK versions below 1.1.9 are deprecated from November 1, 2025, so pin versions and follow the changelog.
Weaver
How can I help you explore Laravel packages today?