Weave Code
Elasticsearch Bundle Laravel Package
markup/elasticsearch-bundle
A Symfony bundle that integrates Elasticsearch into PHP applications, offering configuration, service wiring, and tools for indexing and searching documents. Simplifies client setup and custom index management for Symfony projects.
A Symfony bundle providing simple integration with the Elasticsearch SDK, also providing web profiler information.
Frequently asked questions about Elasticsearch Bundle
- Is markup/elasticsearch-bundle a Laravel package?
- No. It is a Symfony bundle built around a Bundle subclass, a DependencyInjection extension that parses config/packages YAML, tagged service definitions, and a WebProfiler data collector. None of that maps to Laravel's service provider and container model, so it is not a drop-in Laravel package.
- Can I use markup/elasticsearch-bundle in a Laravel application?
- Not directly. You would have to port the Symfony plumbing, and the reusable core—a configured, injectable Elasticsearch client plus index and mapping helpers—is only roughly 100 to 200 lines of glue. Most teams are better off reimplementing that as a Laravel service provider instead of paying the porting tax.
- How do I install markup/elasticsearch-bundle?
- Install it with Composer using composer require markup/elasticsearch-bundle, then register the bundle in your Symfony kernel or bundles.php and add connection and index settings under config/packages. Installation assumes a Symfony application with the bundle and dependency injection wiring in place. In Laravel there is no equivalent registration step because the bundle is not a Laravel package.
- How do I configure Elasticsearch connections and indexes with this bundle?
- Configuration is declarative: you define client connections and their parameters, plus indexes and mappings, in the bundle's YAML configuration rather than in scattered PHP code. The bundle wraps the official Elasticsearch client with sensible defaults and exposes the configured client as an injectable service. That keeps host, auth, and index definitions centralized and reusable across the application.
- Does markup/elasticsearch-bundle support multiple Elasticsearch clusters?
- Yes. The package advertises configurable client connections with support for multiple clusters, so you can define more than one named connection and inject the one you need. In a Laravel port you would reproduce this with a connections array in config/elasticsearch.php and named singleton bindings in the container.
- What Laravel versions does markup/elasticsearch-bundle support?
- None. It is a Symfony bundle and does not ship a Laravel service provider, facade, or config publishing, so Laravel version compatibility is not applicable. If you need Laravel support you should wrap elasticsearch/elasticsearch yourself or use a Laravel-native package such as Laravel Scout with an Elasticsearch driver.
- Is markup/elasticsearch-bundle actively maintained and safe for production?
- The public signals are weak: zero stars, zero dependents, and a composite score of zero, which means no downstream battle-testing and no discoverable security disclosure path. There is a real risk around version coupling, since elasticsearch-php 7.x to 8.x is a breaking client rewrite and a bundle spanning both is expensive to maintain. For a component on the critical path between your app and a data store, treat it as an unhedged dependency and verify commit cadence and maintainer responsiveness first.
- How does markup/elasticsearch-bundle handle logging and errors?
- It provides PSR-compatible logging and error handling around the official Elasticsearch client, so client activity and failures can be routed through your existing PSR-3 logger. The Symfony bundle also includes a data collector for dev-time visibility, but that is built on Symfony's DataCollector lifecycle and does not translate to Telescope or Debugbar without a rewrite. If a collector captures request or response bodies, audit it for PII and hard-gate it to non-production.
- Does markup/elasticsearch-bundle support bulk indexing and query building?
- Yes. The bundle advertises simple document indexing and bulk operations, integrated query building helpers, and declarative index and mapping definitions. It is aimed at the common workflows of indexing documents, running queries, and managing index lifecycle without boilerplate client setup.
- What is the best alternative to markup/elasticsearch-bundle for Laravel?
- Use elasticsearch/elasticsearch directly with a small Laravel service provider that binds a singleton client from config/elasticsearch.php, which is roughly 50 lines and mirrors what the bundle does. If you want higher-level abstractions, Laravel Scout with an Elasticsearch driver or a maintained Laravel-specific Elasticsearch package are better fits. You can still read the bundle's extension and service definitions as a reference for the configuration schema—hosts, auth, retry and backoff, and serializer choice.
Weaver
How can I help you explore Laravel packages today?