- What is sevenspan/laravel-chat and what features does it provide?
- sevenspan/laravel-chat is a Laravel package for adding user-to-user chat to an application. It provides Eloquent models, migrations, and controllers for conversations and messages, plus document sharing, unread counts, and local or S3 uploads. It is aimed at basic one-to-one and group chat rather than a full realtime chat platform.
- How do I install and configure sevenspan/laravel-chat in a Laravel app?
- Install it with Composer, then publish the package config and migrations and run them in a non-production environment first. Review the published schema against your existing messaging or notification tables before adopting package tables as the system of record. Map package models to your User and tenant models and add authorization policies for conversation membership.
- Which Laravel and PHP versions does sevenspan/laravel-chat support?
- The repository does not make version support obvious in the provided context, so check its composer.json constraints and CI matrix before committing. The best-fit target is Laravel 10+ with PHP 8.2+ using MySQL or PostgreSQL and standard Eloquent auth. Pin the package version and test against your exact Laravel and PHP combination.
- Does sevenspan/laravel-chat support real-time messaging or WebSockets?
- The description covers persistence for conversations and messages, not realtime transport. There is no stated WebSocket, broadcasting, presence, or typing-indicator support, so you should plan to add Laravel Echo, broadcasting, or another realtime layer yourself. Adding broadcasting may require extending or forking package internals.
- How are unread message counts and read receipts calculated in sevenspan/laravel-chat?
- The package manages read and unread message counts as part of its conversation and message models. The exact queries and indexes are not described, so review them for your data volume and add indexing or denormalization where needed. Instrument message-list and unread-count queries during a pilot before relying on them at scale.
- Can sevenspan/laravel-chat handle group chats and document sharing?
- Yes, the package is described as supporting one-to-one and group chat with document sharing within conversations. It includes conversation, participant, message, and attachment concepts, but moderation, retention, and advanced group controls remain application responsibilities. Test group membership and document access rules carefully.
- Does sevenspan/laravel-chat support AWS S3 and local file uploads?
- Yes, document uploads can be stored on local disks or AWS S3 according to the package overview. You should still add file validation, virus scanning, retention rules, and signed or policy-controlled access at the application level. Confirm whether URLs use Laravel's filesystem abstraction or assume a specific disk.
- Are authorization policies included for conversations and attachments in sevenspan/laravel-chat?
- The package provides models, migrations, and controllers, but the context does not indicate that full authorization policies are included. Expect to add gates or policies for conversation membership, group roles, and attachment access. Treat document access control and tenant isolation as host-application responsibilities.
- Is sevenspan/laravel-chat production-ready, tested, and actively maintained?
- Treat it as a reference implementation and reusable schema rather than a battle-tested dependency: it has low stars, zero dependents, and a single-vendor maintainer. Check test coverage, CI, semver commitments, and security response before production. Pin versions, review releases, and keep a fork-or-replace decision gate.
- How do I integrate sevenspan/laravel-chat with existing users, tenants, and database schema?
- Publish and review migrations in an isolated branch, diff the schema against existing tables, and avoid adopting package tables as the system of record without review. Map package user references to your existing User and tenant models through a one-off bridge or configuration layer. Confirm that package models are extendable and that published migrations can be modified safely before rollout.