Weave Code
Symfony Bundle Laravel Package
schranz-search/symfony-bundle
Symfony bundle for schranz-search that adds search engine indexing and querying to Symfony apps via a search abstraction layer spanning Elasticsearch, OpenSearch, Meilisearch, Algolia, and more.
An integration of CMS-IG SEAL search abstraction via a Bundle into the Symfony Framework. Part of the https://github.com/php-cmsig/search project. READ-ONLY Repository
Frequently asked questions about Symfony Bundle
- Is schranz-search/symfony-bundle compatible with Laravel?
- No. It is a Symfony bundle that registers services through Symfony's DI container, service tags, and bundle YAML configuration, so there is no Laravel service provider, facade, or config file. For Laravel you should use the underlying framework-agnostic cmsig/search library directly and wire it into a service provider yourself. The bundle itself is only useful in Symfony applications.
- How do I install schranz-search/symfony-bundle?
- Install it with composer require schranz-search/symfony-bundle, then register the bundle in config/bundles.php. Add YAML configuration under config/packages for your chosen adapter and its client library. Finally inject the SEAL Engine service wherever you need indexing or querying.
- Which search engines does this bundle support?
- It supports whatever adapters cmsig/search provides, including Elasticsearch, OpenSearch, Meilisearch, Algolia, Typesense, and others. The bundle is thin glue that wires the selected adapter's client into the container. You install the adapter-specific client library you need and configure it in YAML.
- What Symfony and PHP versions does the bundle require?
- The bundle tracks the parent cmsig/search library, so its declared support matrix follows that project's releases. Check the composer.json of the specific release you pin to confirm supported Symfony and PHP versions before upgrading. Pin versions to avoid transitive adapter breakage.
- Why is the repository read-only and where do I report issues?
- The repository is explicitly READ-ONLY because it is part of the php-cmsig/search monorepo. Issues and pull requests are handled in the parent project rather than here. That governance model is reasonable but couples the bundle's release cadence and bug-fix latency to the monorepo maintainers.
- How do I configure multiple search adapters in Symfony?
- You configure each adapter under config/packages via the bundle's extension, typically selecting one default engine or defining named engines. SEAL's Engine abstraction lets you depend on the interface rather than a specific backend. Switching backends later is mostly configuration plus adapter-specific client setup.
- Is the abstraction truly portable across search engines?
- Partially. Basic full-text search and filters work consistently, but query syntax, analyzers, index mapping, ranking, and facets are not uniformly expressible across Elasticsearch, Meilisearch, Typesense, and Algolia. Expect to write adapter-specific code for advanced features, which reduces the portability benefit. The abstraction pays off mainly if you genuinely expect to switch or run multiple engines.
- How do I use SEAL search in a Laravel app instead?
- Require cmsig/search directly with Composer and bind the Engine and adapter services in a Laravel service provider. Publish a config file for your chosen backend and inject the Engine where needed. You skip the Symfony bundle entirely because the SEAL API is framework-agnostic and portable.
- Is schranz-search/symfony-bundle production-ready?
- It is a thin, conventional Symfony bundle with a small integration surface, so the technical risk is in the wrapper rather than the abstraction. Adoption is low at around 15 stars, which increases the chance that edge cases with Symfony LTS versions or newer adapters go untested. Pin versions and be prepared to own fixes if upstream stalls.
- What are the alternatives to this bundle for search in Symfony or Laravel?
- Use cmsig/search directly and hand-wire it, which is what you would do in Laravel anyway. Alternatively, use backend-specific bundles or clients such as the official Elasticsearch PHP client, Meilisearch's Symfony bundle, or Laravel Scout for Laravel. Choose based on whether you actually need multi-engine portability.
Weaver
How can I help you explore Laravel packages today?