- What is gnugat/search-engine used for?
- It is a lightweight PHP library for adding search to applications with simple indexing and querying abstractions. It keeps search logic decoupled and testable and can be integrated into Laravel or any PHP project. It is a deprecated proof of concept, so treat it as a reference rather than a production dependency.
- Is gnugat/search-engine still maintained?
- No. The repository is marked DEPRECATED and described as a proof of concept. You should not expect new features, security fixes, or support. For new projects, choose a maintained search package or build a small internal abstraction instead.
- How do I install gnugat/search-engine with Composer?
- You can require it with Composer using the package name gnugat/search-engine, assuming the legacy repository is still reachable. Because the project is deprecated, pin the exact version and review the code before adding it to an application. In Laravel, you would then wire the library's abstractions into your own service provider.
- Does gnugat/search-engine work with Laravel?
- Yes, it is designed as a framework-agnostic PHP library that can be integrated into Laravel or any PHP project. Laravel-specific integration is manual: you bind the indexing and querying abstractions in your app. It is not a Laravel-first package with published framework conventions.
- Which Laravel versions are supported by gnugat/search-engine?
- The package is a plain PHP library, so its compatibility depends on the PHP version it targets rather than a declared Laravel version. The repository is legacy and deprecated, so there is no current Laravel support matrix. Test it against your exact Laravel and PHP versions before relying on it.
- How do indexing and querying work in gnugat/search-engine?
- The library provides simple indexing and querying abstractions that keep search logic decoupled from your application code. You index records through its indexing abstraction and issue queries through a separate query layer. This separation makes the search logic easier to test and swap out.
- Can I use gnugat/search-engine in production?
- It is explicitly deprecated and labeled a proof of concept, so it is not a good production choice. Production search needs maintenance, security updates, and operational guarantees that this legacy project does not provide. Use it only for learning or as inspiration for your own abstraction.
- How do I test search logic with gnugat/search-engine?
- The decoupled indexing and querying abstractions are intended to make search logic testable in isolation. You can unit-test your own indexers and query objects without booting a full search backend. In Laravel, use the usual PHPUnit setup and mock or fake the library's interfaces.
- What are good alternatives to gnugat/search-engine for Laravel?
- For Laravel, consider maintained options such as Laravel Scout with a driver like Meilisearch, Algolia, or the database driver. If you only need simple filtering, Laravel's query builder and Eloquent scopes may be enough. Choose a package with active maintenance and declared support for your Laravel version.
- Is gnugat/search-engine a full search engine like Elasticsearch?
- No. It is a lightweight PHP library that demonstrates search indexing and querying abstractions; it is not a standalone search server. It does not replace Elasticsearch, Meilisearch, or Algolia. It is better understood as a way to decouple search logic in your code.