- What is lunarphp/meilisearch used for in a Laravel application?
- It is a Meilisearch integration for Lunar, the Laravel e-commerce framework. It is intended to add fast, typo-tolerant product search with filtering, sorting, and instant results for storefront catalogs. Treat it as a search integration layer for Lunar rather than a standalone search engine.
- Which Laravel, PHP, and Lunar versions does lunarphp/meilisearch support?
- The provided release notes do not list supported Laravel, PHP, or Lunar versions. Check the package composer.json metadata and README before installing. Because 0.1.0-rc.2 is pre-1.0, verify compatibility in a branch with Composer dry-run against your app's exact versions.
- How do I install lunarphp/meilisearch with Composer?
- Install it with an explicit RC constraint, such as the 0.1.0-rc.2 release, so Composer does not silently resolve to a different version. Run a Composer dry-run in a branch first to confirm resolution against your Laravel, PHP, Lunar, and Meilisearch SDK constraints. Then configure the package and connect it to a disposable Meilisearch instance for validation.
- Which Meilisearch server versions work with meilisearch-php ^0.26.1?
- The release notes only state that the package requires meilisearch/meilisearch-php ^0.26.1; they do not list compatible Meilisearch server versions. Check the meilisearch-php ^0.26.1 documentation and test against your intended server version. SDK and server version mismatch is a known feasibility gate before production use.
- Does lunarphp/meilisearch provide indexing, filtering, sorting, and reindex commands?
- The package is described as adding Meilisearch-backed product search with filtering, sorting, and instant results for Lunar. The release notes do not detail index schema, model observers, search API surface, multi-store scoping, or reindex commands. Confirm these behaviors in the README and source, and validate them on a representative catalog subset before relying on them.
- Is lunarphp/meilisearch compatible with Laravel Scout?
- The provided assessment does not confirm Scout compatibility or conflict. It recommends confirming that the package complements rather than conflicts with Laravel Scout, existing search drivers, queue workers, and catalog indexing jobs. Test both in a non-production spike if your app already uses Scout.
- Can I use lunarphp/meilisearch in production?
- Treat 0.1.0-rc.2 as pilot-grade rather than a settled production component. Start with a non-production spike, validate search parity, filters, sorting, reindex behavior, latency, and rollback before replacing an existing search path. Promote to staging and canary only after operational checks pass.
- Does lunarphp/meilisearch have tests and documentation for upgrading?
- The release notes do not describe test coverage, documentation quality, or a stable upgrade path. Because the package is pre-1.0 and this release is dependency-only, confirm issue response, docs, and ownership before customer-facing use. Plan to monitor upstream releases and pin the RC explicitly.
- What happens if Meilisearch is unavailable or indexing fails?
- The package context does not describe a built-in fallback search path. Define fallback behavior, monitoring, and rollback before rollout, covering Meilisearch outage, index drift, failed reindex jobs, and SDK/server mismatch. Degraded search latency and index rebuild time should also be part of your operational plan.
- What alternatives should I consider to lunarphp/meilisearch?
- Evaluate Laravel Scout with a Meilisearch driver or your existing search driver, especially if you need a more established integration path. Compare Composer compatibility, Meilisearch server support, indexing and reindex features, and operational ownership. Run a small catalog spike to compare relevance, filters, sorting, and latency before choosing.