- Can I use ibexa/search in a Laravel application?
- No. ibexa/search is the search subsystem of Ibexa DXP, not a general-purpose search library, and it expects Ibexa's service container, Repository/ContentService domain model, and search engine abstraction. There is no Laravel service provider, facade, or config stub, so integrating it would mean reimplementing the platform.
- How do I install ibexa/search with Composer?
- You normally do not install it directly. It is a read-only split of the Ibexa monorepo and arrives as a transitive dependency when you run Ibexa DXP. Standalone installation gives you code that cannot boot without the platform's container registrations and repository contracts.
- What PHP and Symfony versions does ibexa/search require?
- The 5.0 branch requires PHP 8.3 or newer and pins Symfony components to ^7.3/^7.4, while the 4.6 branch is maintained in parallel for LTS conservatism. Those strict pins can collide with Laravel 11/12's own Symfony constraints during Composer resolution. Expect to adjust constraints or maintain a Composer patch if you attempt to combine them.
- Is ibexa/search free to use in a commercial Laravel product?
- It is dual-licensed under the Ibexa Business Use License, which requires a paid Ibexa DXP subscription, or GPLv2. GPLv2 is copyleft, so distributing a Laravel product that links this code is a legal question for counsel, not an engineering decision. Treat licensing as a blocking gate before any technical work.
- What is the difference between ibexa/search 4.6 and 5.0?
- Both branches are live and released in near-lockstep with Ibexa DXP. Branch 5.0 raised the PHP floor to 8.3, moved to Symfony 7.4 LTS, and dropped the class_alias backward-compatibility layer; branch 4.6 is the more conservative LTS choice. Pick one deliberately and record why.
- Can I use ibexa/search for facets, autocomplete, and spell check in Laravel?
- The capability exists inside Ibexa DXP, but it is wired to Ibexa's Twig/admin UI layer and search engine abstraction rather than exposed as a standalone API. You cannot lift facets, sorting, autocomplete, or suggestions into Laravel without the surrounding platform. Laravel Scout with Meilisearch or Typesense covers roughly 80% of that surface with no copyleft exposure.
- What Laravel alternative should I use instead of ibexa/search?
- Use Laravel Scout with Meilisearch or Typesense for a native Eloquent-integrated search layer. Both give you filtering, facets, sorting, and typo tolerance without Ibexa's licensing or Symfony version lockstep. This is the recommended path when the goal is search for a Laravel app rather than Ibexa DXP itself.
- How can Laravel query Ibexa search if Ibexa DXP is already in our stack?
- Treat search as a remote service. Laravel calls Ibexa's public REST or GraphQL endpoints for query, facet, sort, and suggestion data, while ibexa/search stays inside the CMS deployment and upgrades with the DXP. This keeps a clean boundary, avoids vendor-tree coupling, and lets Laravel cache and reshape responses on its own terms.
- Can I test ibexa/search without Ibexa DXP?
- Not realistically. The package depends on Ibexa's DI extensions, repository contracts, and search services, and it ships no standalone test harness or Laravel-adjacent examples. Any meaningful test requires a booted Ibexa DXP instance.
- Is ibexa/search actively maintained and safe for production in a Laravel app?
- It is maintained, but only on Ibexa's release schedule. Branches 4.6 and 5.0 are released in near-lockstep with the DXP, and low adoption outside Ibexa means little community support. For production in Laravel the technical risk is high: licensing, PHP/Symfony lockstep, and Composer conflicts all apply, so it is not a safe dependency without an existing Ibexa DXP estate.