- What does genealabs/laravel-tenancy-scout do?
- It integrates Laravel Scout with the GeneaLabs Laravel Tenancy package so search indexing and querying become tenant-aware. The package supplies Scout commands that keep models, indexes, and results scoped to the current tenant. In practice, each tenant searches only its own records instead of a shared index.
- How do I install genealabs/laravel-tenancy-scout?
- Install it with Composer using the package name genealabs/laravel-tenancy-scout. Laravel Tenancy and Laravel Scout should already be installed and configured in the application. Review the repository README for any service provider registration or configuration steps, and pin an exact version because the package is pre-1.0.
- Does genealabs/laravel-tenancy-scout support Laravel 11?
- Release 0.4.0 states Laravel 11 compatibility, so it is the version to evaluate for a Laravel 11 application. The release note does not say whether Laravel 9 and 10 support remains or was dropped. Check the composer.json constraints and run your own test suite before adopting it.
- Is this package compatible with Laravel 10 or Laravel 9?
- That is not confirmed by the available information, which only cites Laravel 11 compatibility in release 0.4.0. The key question is whether the change was additive or substitutive. Inspect composer.json and the release history, and treat older Laravel support as unknown until verified.
- Do I need Laravel Scout and Laravel Tenancy installed first?
- Yes. This package is an integration layer for GeneaLabs Laravel Tenancy and Laravel Scout, so both should be installed and working first. It then provides Scout commands that make indexing and querying respect the current tenant. Confirm your Scout driver and tenancy bootstrapping are configured before adding it.
- How do I make Scout indexes tenant-aware in a multi-tenant Laravel app?
- The package scopes Scout models, indexes, and results to the current tenant so searches do not leak across tenants. Ensure the current tenant is set before indexing or querying, including inside queue workers and console commands. Review the package configuration and test tenant switching explicitly in your application.
- Can I use genealabs/laravel-tenancy-scout in production at version 0.4.0?
- It is possible, but treat it as pre-1.0 software with no stability promise. Minor releases may contain breaking changes, so pin the exact version and test upgrades in staging. Also review the maintainer activity and release cadence before relying on it in production.
- How should I test tenant-scoped Scout search results?
- Create at least two tenants with separate records, index them, switch tenant context, and assert that each search returns only that tenant's data. Test queue workers and console commands because indexing often runs outside the HTTP request. Include these checks in CI, especially if you are evaluating Laravel 11 support.
- What are the alternatives to laravel-tenancy-scout?
- You can implement tenant scoping manually with Laravel Scout by using per-tenant index names and tenant-aware query constraints. Some tenancy ecosystems also provide their own Scout integrations, so compare maintenance and Laravel version support. Consider whether the package's commands save enough work versus maintaining a small custom integration.
- How actively is genealabs/laravel-tenancy-scout maintained?
- The available evidence is limited to release 0.4.0 and its Laravel 11 compatibility note. There is no supplied information on test coverage, download counts, or a CI matrix. Check the GitHub repository for release history, maintainer activity, and plans for future Laravel versions before adopting it.