Weave Code
Elasticsearch Bundle Laravel Package
sineflow/elasticsearch-bundle
Symfony bundle for integrating Elasticsearch into PHP applications. It streamlines client configuration, service wiring, and index/query workflows so you can add search features using the official Elasticsearch client.
Sineflow ElasticsearchBundle is a Symfony bundle that integrates Elasticsearch into Symfony applications with minimal boilerplate. It provides framework-native configuration and services for connecting to Elasticsearch, managing indexes, and performing search operations through Symfony’s service container.
- Configurable Elasticsearch client services
- Index and document management support
- Search and query integration
- Native Symfony dependency injection setup
- Reusable services for indexing and retrieval
Frequently asked questions about Elasticsearch Bundle
- Does sineflow/elasticsearch-bundle work with Laravel?
- It is a Symfony bundle, not a Laravel package, so it will not register itself in a Laravel application because there is no Symfony Kernel to boot it against. Composer installation will likely succeed since Laravel already pulls in Symfony components, but you would have to bootstrap the bundle manually inside Laravel's container, which neither ecosystem supports. In practice you end up using the underlying official elasticsearch/elasticsearch client directly anyway.
- How do I install and configure sineflow/elasticsearch-bundle in a Laravel app?
- Running composer require may work, but there is no config publishing, no Laravel service provider, and no bundle registration hook. You would need to register the bundle's DI extension and load its YAML configuration by hand against Laravel's container, which is fragile and more effort than a native integration. The recommended path is to skip the bundle and bind the official client in your own service provider.
- Which PHP, Symfony, and Laravel versions does this bundle support?
- The available context does not document a CI matrix, a PHP version floor, or explicit Symfony DI 6 and 7 coverage, so treat version support as unverified. Symfony bundles typically target specific Symfony majors, and Laravel's Symfony component versions move independently, so compatibility is not guaranteed. Check the composer.json constraints and test against your runtime before committing.
- Which elasticsearch-php client and Elasticsearch server versions does it support?
- The pinned elasticsearch-php major is not stated in the assessment, and that matters because the client has had breaking changes across majors in the transport layer and typed endpoints. You need to confirm whether the pin supports Elasticsearch 8 or 9 servers and how product-check enforcement is handled. Pin the server major and the client major together and treat upgrades as coupled events.
- What should I use instead of this bundle in a Laravel application?
- Build a small native integration: composer require elasticsearch/elasticsearch directly, add a config/elasticsearch.php file for hosts, credentials, timeouts, and retry settings, and bind a singleton client via ClientBuilder in a service provider. Add a thin repository or query layer so application code never touches the raw client. The assessment estimates this at roughly half a day to one engineering day.
- Does this bundle do anything beyond constructing the Elasticsearch client?
- Based on the assessment, its substance is a Symfony DI extension, a configuration tree, service definitions, and an autowiring alias that builds the official client from YAML. The package description mentions index management, query helpers, and repository-style search, but the assessment questions whether anything beyond client construction is implemented and tested. Verify features like health checks, profiler integration, or console commands before relying on them.
- Is sineflow/elasticsearch-bundle production-ready and well maintained?
- The maintenance signals are weak: around 8 stars, 0 dependents, a single apparent maintainer, and no visible CI or compatibility testing. There is also no documented security disclosure path, which is a real concern for anything sitting in your search data path. For a production Laravel app, the safer option is a small integration your team owns and can test.
- Why is the latest release tagged 2026-07-14, and is that a problem?
- A future-dated tag is a provenance red flag that should be explained before adoption. It could be a scheduled tag, clock skew, or a rewritten history, and none of those are confirmed by the available context. Check whether the tag is signed and who authored it before pinning it in a production project.
- How does this compare to Laravel Scout or a custom service provider?
- Scout is a Laravel-native search abstraction with official driver support and a well-known integration path, while this package is Symfony-oriented wiring you would have to hand-bootstrap in Laravel. A custom service provider around the official client gives you full control in roughly 40 to 80 lines of code. Choose Scout if you want a framework-integrated search layer, or a custom provider if you need direct Elasticsearch query control.
- How much work is it to migrate off this bundle to a native Laravel setup?
- The assessment estimates 0.5 to 1 engineering day to build the config file, a service provider with a singleton ClientBuilder client, a thin repository layer, and an artisan health command for deploy gates. Adopting the bundle instead is estimated at 2 to 3 days of fighting a bundle-less boot plus ongoing fork maintenance. The native build is cheaper and produces an asset your team owns.
Weaver
How can I help you explore Laravel packages today?