- Is search/sphinxsearch-bundle compatible with Laravel?
- No. It is a Symfony 2 bundle that relies on Symfony's DI container, bundle registration, and YAML or XML service configuration, so it cannot be installed and enabled as-is in a Laravel application. Laravel has no equivalent bundle bootstrapping. You would need to extract the underlying SphinxClient and wire it through a Laravel service provider yourself.
- Can I install search/sphinxsearch-bundle in Laravel 10 or 11 with Composer?
- Composer may allow the download, but the package will not function because it expects Symfony 2 kernel and container APIs. It provides no Laravel service provider, facade, or Artisan commands. Treat it as a reference implementation, not a dependency you can require and use directly.
- Does search/sphinxsearch-bundle provide a Laravel service provider or facade?
- No. The package only ships Symfony 2 bundle classes, configuration, and a thin wrapper around the legacy sphinxapi.php SphinxClient. There is no Laravel service provider, facade, config file, queue integration, or Eloquent query-builder hook. All Laravel integration is net-new work for your team.
- What is search/sphinxsearch-bundle actually useful for in a Laravel project?
- It is useful as a reference for the SphinxClient protocol implementation and for its configuration conventions around indexes and searchd. You can vendor the BSD-2-Clause licensed SphinxClient class and reproduce the config semantics in config/search.php. The rest of the bundle is Symfony-specific and not reusable in Laravel.
- Is Sphinx Search still maintained, and does this package work with Manticore?
- Sphinx Search is end-of-life upstream; the actively maintained successor is Manticore Search, a fork of Sphinx 2.3. The bundle targets the legacy sphinxapi binary protocol on port 9312, which is broadly stable, but version negotiation against Manticore releases and the newer HTTP/JSON endpoint differs. If you adopt this approach, plan for Manticore compatibility rather than Sphinx 3.x binaries.
- What PHP versions does search/sphinxsearch-bundle support?
- The codebase is from the Symfony 2 and PHP 5.3 to 5.5 era. It likely uses constructs removed in PHP 8, such as each(), old-style constructors, dynamic properties, and implicit nullable parameters. Assume the client needs patching before it runs on a modern PHP 8.x runtime.
- How do I test Sphinx search integration in Laravel?
- Because the package has no Laravel testing helpers, you would test your own wrapper around the vendored SphinxClient. Use a fake or mock client behind a SearchDriver contract so unit tests do not require a running searchd instance. Integration tests can hit a disposable Manticore container, but keep them separate from fast test suites.
- What are the alternatives to search/sphinxsearch-bundle for Laravel?
- Laravel Scout with Meilisearch, Typesense, Algolia, or Elasticsearch and OpenSearch drivers are the mainstream alternatives. For smaller corpora, MySQL or PostgreSQL full-text search with proper indexing may be enough. Choosing a Sphinx client narrows your exit path to Manticore unless you rewrite the query layer.
- Is search/sphinxsearch-bundle safe for production?
- Abandonment risk is high: roughly 40 stars, zero dependents, a Symfony 2-era codebase, and no security advisory process. Runtime risk is also high on PHP 8 because the code predates modern language changes. If you use it, vendor and fork the client, wrap it in a first-party package, and own maintenance explicitly.
- Should I use search/sphinxsearch-bundle or build a custom Laravel Sphinx driver?
- Build a custom driver rather than adopting the bundle. Define a SearchDriver contract up front, implement a Sphinx or Manticore client behind it, and keep the option to add Meilisearch or Typesense later. This avoids Symfony coupling and gives you a supported-looking internal package with a stable namespace.