Weave Code
Search Laravel Package
capell-app/search
Search integration for Capell applications, adding configurable search across models and content. Built for Laravel, it supports indexing, querying, and extension points for tailoring results and building custom search experiences.
Production-grade site search for Capell with relevance-tuned results, synonyms, typo tolerance, curated promotions, and admin search insights.
Frequently asked questions about Search
- What is capell-app/search used for in Laravel?
- capell-app/search adds a search layer to Laravel applications, primarily for Capell CMS content and models. It provides model indexing, fluent query and filter building, sorting, pagination, and extension points for custom search logic. It is most valuable when you are already using the Capell package set; for general-purpose search outside Capell, a narrower abstraction may be a better fit.
- How do I install and configure capell-app/search?
- Install it with Composer and let Laravel package auto-discovery register the service provider. Publish the package configuration, choose your search driver, then define which models or content types are indexable and run an initial index build. The evaluation notes that configuration is expected to be driver-driven; confirm the exact config keys in the published config file before wiring it into existing app config.
- Which Laravel and PHP versions does capell-app/search support?
- The package is positioned for Laravel 10, 11, and 12 with PHP 8.2 or newer, but that support matrix should be verified against the package's composer.json and any published CI matrix. Because Capell packages move in lockstep, check the Laravel and PHP constraints of the full Capell dependency set, not just this package. Pin exact or narrow versions if you need predictable upgrades.
- Which search drivers does capell-app/search support?
- The package is described as driver-agnostic, but the technical evaluation explicitly flags first-party versus community driver support as an open question. Check the README and config for the drivers that actually ship, such as a database driver or external engines like Meilisearch, Algolia, or Typesense. Choose the driver before writing integration code because it determines your infrastructure and migration plan.
- Do I need queue workers for indexing with capell-app/search?
- Indexing is part of the package's model indexing and result retrieval workflow, and queue workers are expected for asynchronous indexing in the integration approach. The database driver minimizes infrastructure but has practical scale limits; external engines add a service dependency but remove that ceiling. Confirm whether your chosen driver indexes synchronously or through queued jobs before sizing workers.
- Can I use capell-app/search without adopting the full Capell CMS?
- It can technically be used in custom Laravel search workflows, but its strongest fit is applications already inside or intentionally adopting the Capell package set. Outside Capell, you carry coupling to Capell conventions and sibling package version constraints without getting the CMS-scoped integration benefits. If you only need a general search abstraction, Laravel Scout or a thin engine wrapper usually carries less coupling.
- How do I upgrade capell-app/search safely, and is a reindex required?
- Treat upgrades carefully: the evaluation notes that index schema and driver contracts can shift even in patch releases, and v1.0.48 shipped a link-only changelog. Review the diff, pin versions, and test index builds against a staging dataset before upgrading production. Ask whether schema changes are versioned with migrations and whether a full reindex is mandatory; do not assume a patch bump is risk-free.
- Does capell-app/search support multi-site or multi-tenant content scoping?
- The evaluation lists multi-site and multi-tenant content scoping as a key question rather than a confirmed feature. Check the package docs and config for native site or tenant scoping before designing around it. If it is not built in, you will need to add scoping in your index definitions and queries, which increases custom code and upgrade risk.
- How does capell-app/search compare to Laravel Scout?
- Laravel Scout is the mainstream choice for general-purpose model search and has broader adoption and documentation. capell-app/search differentiates through Capell integration: content-event hooks, CMS-scoped indexing, and a consistent query layer for Capell projects. Consolidating onto Capell can justify the switch, but replacing Scout means re-expressing event hooks, index definitions, and relevance tuning.
- How should I test and monitor capell-app/search in production?
- Test with a staging index and a sampled query workload, and monitor for silent failures such as empty result sets rather than thrown exceptions. The project has a small maintainer team and narrow adoption relative to mainstream search packages, so bus factor and changelog transparency are the main long-term risks. Dual-run old and new search paths behind a flag before cutover, and keep a documented reindex procedure with expected downtime.
Weaver
How can I help you explore Laravel packages today?