Weave Code
Solr Bundle Laravel Package
integrated/solr-bundle
A Symfony bundle for integrating Apache Solr into PHP applications. It provides configuration and services for indexing content and running fast, scalable full-text search queries, helping teams add Solr-powered search with less boilerplate and tighter framework integration.
Adds support for Solr configuration and indexing of your documents or entities
Frequently asked questions about Solr Bundle
- Is integrated/solr-bundle compatible with Laravel?
- No, it is a Symfony bundle rather than a Laravel package. It assumes Symfony framework-bundle, a DependencyInjection extension, and YAML or XML service definitions, none of which Laravel consumes. Treat Laravel compatibility as unproven with a strong prior of no, and verify by attempting to instantiate the indexing services without a Symfony kernel.
- How do I install integrated/solr-bundle?
- Install it with Composer using integrated/solr-bundle, then register the bundle in a Symfony kernel and configure your Solr connections, cores, and endpoints. In Laravel there is no bundle registration path, so installation alone does not make it usable. Check the repository for the supported Symfony and PHP version matrix before committing.
- How do I configure multiple Solr cores and endpoints in integrated/solr-bundle?
- The package provides declarative configuration for connections, cores, and endpoints, plus extensible definitions for custom field mappings. In Symfony you would define those values in the bundle config tree rather than scattering connection logic through your code. In Laravel you would need to reproduce that configuration manually, which is a sign the integration is not native.
- Which Solr client library does integrated/solr-bundle depend on?
- The low-level Solr client is a transitive dependency, likely Solarium, but you should verify the pinned major in composer.json. The bundle wraps that client behind service definitions and configuration. Confirm that the underlying client is maintained and compatible with your PHP version before relying on it.
- Which Apache Solr versions are supported by integrated/solr-bundle?
- The provided context does not document a clear Solr version support matrix. Bundle-era code often targets older schema assumptions, and Solr 8 versus Solr 9 API differences matter. Verify schema and API compatibility in code before using it in production.
- Does integrated/solr-bundle manage Solr schema or only index documents?
- It provides declarative index and field configuration plus document add, update, and delete operations. It does not appear to deliver schema migration, admin UI, or relevance tooling. Assume it pushes documents into an existing Solr core unless code review proves otherwise.
- Is integrated/solr-bundle actively maintained?
- Maintenance signals are weak: zero stars, zero dependents, single-vendor origin, and an unclear last commit date. That implies a bus factor of one and real abandonment risk in your search path. An unmaintained search dependency can become a blocker for PHP and framework upgrades.
- Can I use integrated/solr-bundle without Symfony?
- Possibly, but only if the core indexing services can be instantiated without Symfony's service container. Most of the package's value sits in its DI extension and service definitions, which are Symfony-specific. Run a short spike to instantiate the services without a kernel; if that fails, go directly to Solarium or Laravel Scout.
- How does indexing work in integrated/solr-bundle: Doctrine hooks or explicit service calls?
- The package provides services for batch indexing, updates, and deletes, but the trigger mechanism needs verification. Doctrine lifecycle hooks would not port to Eloquent, while explicit service calls are more portable. Check the code before assuming Laravel model events can drive indexing.
- What are alternatives to integrated/solr-bundle for Solr in Laravel?
- Use solarium/solarium behind a thin repository or service layer that you own and maintain. Alternatively, use Laravel Scout with a maintained Solr driver if you want Eloquent-searchable ergonomics. Both approaches avoid inheriting an unmaintained Symfony wrapper and its container assumptions.
Weaver
How can I help you explore Laravel packages today?