- What is get-stream/stream-laravel used for in Laravel?
- It is the official Laravel integration for GetStream.io activity feeds, adding newsfeeds, follow relationships, notification feeds, feed enrichment, and real-time updates to Laravel apps. It fits teams willing to depend on the hosted GetStream.io service and wanting Eloquent model integration, a Stream facade, config publishing, and a Laravel notification channel. It is a thin integration, not a self-contained feed engine, and it is in maintenance mode.
- How do I install get-stream/stream-laravel?
- Install it with Composer using composer require get-stream/stream-laravel, then publish the package config and set your GetStream.io API credentials. Define your feed groups in Stream and wire domain events or model changes to activity writes. Because the package is in maintenance mode, pin versions and run a compatibility spike against your Laravel and PHP matrix before committing.
- Which Laravel and PHP versions are supported by get-stream/stream-laravel?
- The package README and Composer constraints are the source of truth, but the last release was 2023-03-16, so support for current Laravel and PHP versions must be proven. Run a compatibility spike against your target Laravel and PHP versions and the Stream PHP SDK version you plan to use. If the package lags, evaluate a maintained fork or direct SDK integration rather than forcing an outdated dependency.
- How do I configure GetStream.io credentials for the Laravel package?
- Publish the package config, then provide your GetStream.io API key and secret through environment variables or your secret management system. Define feed groups in the Stream dashboard and keep credentials out of source control. Restrict outbound HTTPS to Stream endpoints and verify config keys against the README for your pinned package version.
- Does get-stream/stream-laravel support Eloquent models, follows, notification feeds, and real-time updates?
- The package is described as supporting Eloquent model integration, a Stream facade, config publishing, and a Laravel notification channel for GetStream.io Feeds v2. Feed groups, follows, enrichment, ranking, notifications, moderation, and real-time updates are capabilities of the hosted Stream service, so confirm the exact API surface exposed by your pinned package and SDK. It does not provide a self-contained feed engine inside Laravel.
- Can I test get-stream/stream-laravel without a live GetStream.io account?
- Do not assume the package ships a complete offline fake for the hosted service, because it is a thin integration. Wrap it behind an app-owned FeedService or repository interface and mock that boundary in unit tests, then run integration tests against a Stream sandbox or test account. Confirm current mocking options in the Stream PHP SDK before relying on them.
- Is get-stream/stream-laravel still maintained, or should I use getstream-php?
- It is in maintenance mode and has been superseded by Feeds v3, with the last release on 2023-03-16. For new projects, the package overview points to getstream-php rather than this Laravel package. If you keep it, pin versions, assign ownership, and plan for a maintained fork or direct SDK migration.
- What production risks should I consider with get-stream/stream-laravel?
- Material risks include vendor lock-in, pricing changes, API drift, rate limits, outage behavior, privacy and DPA terms, and data residency. The package also has a 2023 release and weak ecosystem signals, so compatibility with current Laravel, PHP, and the Stream PHP SDK must be proven. Use queued writes, retries, caching, degradation, and a documented exit and backfill plan.
- How should I handle activity writes and feed fan-out with this package in Laravel?
- Keep Stream calls out of user-facing request paths where possible, and dispatch queued jobs for activity writes and feed fan-out triggers. Use Laravel queues with Redis and Horizon or your existing queue for retries, backpressure, and dead-letter handling. Wrap the vendor facade behind an app-owned FeedService so you can test, degrade, and migrate independently.
- What alternatives or migration path exist if I leave GetStream.io?
- For new work, evaluate getstream-php or Feeds v3 directly, and compare against database-backed feeds if data residency or deep custom control matters. If leaving Stream, wrap the integration behind an app contract, use shadow reads or dual-write, backfill historical activities, reconcile counts, then cut over reads after consistency checks. Keep a degraded fallback for vendor outages.