Drives a searchez::Backend behind adminx-core’s Indexer seam. The
whole integration is these three methods mapping one neutral vocabulary onto
the other.
Register a search backend with adminx-core. Use init_memory for the
batteries-included path, or this to supply a configured backend (e.g.
searchez::MeilisearchBackend).
Register searchez’s in-memory BM25 backend. No external service — ideal for
development and small single-process datasets. Non-persistent, so run
reindex at startup (or after a restart) to repopulate it from the
database.
Backfill a resource’s index from a set of already-loaded rows. Each row is
mapped through the resource’s search_fields() and its primary key. Run this
to seed a new index, after switching backends, or on startup for the
non-persistent in-memory backend.