- Is mitru/elasticsearch-bundle a Laravel package?
- No. It is a Symfony bundle, built around Symfony's Kernel, Bundle base class, DI extension, and Configuration tree, none of which exist in Laravel. It has no Laravel service provider, facade, or package auto-discovery entry, so Composer will install it but Laravel will not wire anything for you. Treat it as a Symfony component, not a Laravel search package.
- Can I use a Symfony bundle like mitru/elasticsearch-bundle inside a Laravel application?
- Technically yes, but only by bypassing the bundle and instantiating the underlying Elasticsearch client yourself, which throws away the package's only real value: the Symfony DI wiring. There is no auto-discovery path into Laravel's container, and no evidence the client-construction logic is separated from Symfony-bound abstractions. You would own bespoke glue indefinitely, and that cost usually exceeds adopting the official client directly.
- Does mitru/elasticsearch-bundle work with Laravel Scout?
- No. Laravel Scout integrates through dedicated Scout drivers, and this bundle provides none. Scout expects an engine class implementing Laravel's Engine contract plus indexing lifecycle hooks, observers, and queue support, which a Symfony bundle does not supply. If you want Scout, use a maintained Elasticsearch driver instead.
- Which Elasticsearch and PHP versions does mitru/elasticsearch-bundle support?
- The supported matrix is not clearly documented, so verify composer.json constraints before any design work. It likely targets an older Elasticsearch generation such as 5.x through 7.x and older PHP versions. Composer resolution against PHP 8.2 or 8.3 and current symfony/* contracts is a live risk and should be the first thing you test.
- Does mitru/elasticsearch-bundle wrap the official elasticsearch/elasticsearch client?
- This is unclear and must be confirmed by reading its composer.json and source. If it depends on the official client, that client is the only part worth keeping under Laravel. If it hand-rolls HTTP calls, expect missing retry, backoff, connection reuse, and typed error handling, all of which matter in production.
- Is mitru/elasticsearch-bundle actively maintained?
- There is effectively no adoption signal: zero stars, zero dependents, a composite score near zero, and a single maintainer. No CI pipeline or test suite is visible, and there is no community to catch regressions. Treat it as unmaintained and plan accordingly, even though the MIT license itself is fine.
- How do I install and configure mitru/elasticsearch-bundle in a Laravel app?
- There is no supported Laravel installation path. You would require it with Composer, then manually construct the client and reimplement connection pooling and configuration that the Symfony bundle normally provides. That is bespoke integration work you would maintain forever, and it is not recommended for new Laravel projects.
- What are the best alternatives to mitru/elasticsearch-bundle for Elasticsearch in Laravel?
- Bind the official elasticsearch/elasticsearch client as a singleton in a small Laravel service provider and build a repository or query-builder layer your team owns. If your search needs are simple full-text queries over Eloquent models, laravel/scout with a maintained Elasticsearch driver is the lower-effort, more idiomatic path. Both give you supported dependencies and avoid Symfony-specific glue.
- What production risks come with using mitru/elasticsearch-bundle?
- The main risks are abandonment, bus factor, and unverified compatibility with current PHP and Symfony versions. With no dependents or CI, regressions and security issues are unlikely to be caught, and a hand-rolled transport may lack retries and typed error handling. Isolate any existing usage behind an interface and plan a replacement rather than expanding it.
- Can I migrate away from mitru/elasticsearch-bundle to the official Elasticsearch PHP client?
- Yes, and it is straightforward if you keep the boundary narrow. Define a domain interface such as SearchGateway, implement it once against the bundle and once against the official client, then cut over behind a feature flag. For greenfield Laravel work there is nothing to migrate, so skip the bundle and start with the official client or Scout.