A Directus 9 extension that automatically syncs content with external search engines like MeiliSearch, ElasticSearch, and Algolia.
SearchSync is a Directus extension that automatically indexes content from Directus collections into external search engines like MeiliSearch, ElasticSearch, and Algolia. It ensures search indices stay synchronized with content changes in real-time and provides flexible configuration for data transformation and filtering. This enables powerful, up-to-date search functionality for applications built on the Directus headless CMS.
Directus developers and administrators who need to integrate robust, real-time search capabilities into their applications using external search engines. It is particularly useful for teams managing content-heavy Directus projects where manual search index synchronization is impractical.
Developers choose SearchSync for its unified, multi-engine support and automatic indexing, which eliminates manual synchronization efforts. Its flexible configuration, including custom data transformations and batch processing, offers a balance of simplicity for common use cases and adaptability for complex scenarios.
Simple Directus 9 extension that sync content with remote search engine.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports MeiliSearch, ElasticSearch, and Algolia through a unified configuration block, allowing teams to switch engines without rewriting integration code, as detailed in the README's server type examples.
Automatically updates search indices on content creation, update, or deletion in Directus, eliminating manual synchronization efforts and keeping search results current.
Enables custom JavaScript functions to format or enrich data before indexing, such as stripping HTML tags or flattening objects, demonstrated in the .searchsyncrc.js example with utility functions.
Handles large datasets with configurable batch limits (default 100) during indexing or reindexing, preventing performance issues in high-volume Directus collections.
Relies on cosmiconfig for file-based setup (e.g., .searchsyncrc.json or .js), requiring developers to manage JSON/JS configurations manually without a GUI, which can be error-prone for less technical users.
The README lacks details on handling indexing failures, retries, or monitoring, leaving developers to implement their own error recovery strategies without guidance.
Only handles backend indexing; frontend search implementation must be built separately using the search engine's SDK, adding to development time and complexity.