mirror of
https://github.com/meilisearch/meilisearch.git
synced 2024-12-18 17:35:58 +08:00
A lightning-fast search API that fits effortlessly into your apps, websites, and workflow
app-searchdatabaseenterprise-searchfacetingfull-text-searchfuzzy-searchgeosearchhybrid-searchinstantsearchrestrustsearchsearch-as-you-typesearch-enginesemantic-searchsite-searchsynonymstypo-tolerancevector-databasevectors
2f1a9105b9
Some checks failed
Test suite / Tests on ${{ matrix.os }} (macos-13) (push) Waiting to run
Test suite / Tests on ${{ matrix.os }} (windows-2022) (push) Failing after 23s
Test suite / Tests on ubuntu-20.04 (push) Failing after 13s
Test suite / Tests almost all features (push) Has been skipped
Test suite / Test disabled tokenization (push) Has been skipped
Test suite / Run tests in debug (push) Failing after 12s
Test suite / Run Clippy (push) Successful in 9m3s
Test suite / Run Rustfmt (push) Successful in 2m44s
Run the indexing fuzzer / Setup the action (push) Successful in 1h6m48s
Indexing bench (push) / Run and upload benchmarks (push) Has been cancelled
Benchmarks of indexing (push) / Run and upload benchmarks (push) Has been cancelled
Benchmarks of search for geo (push) / Run and upload benchmarks (push) Has been cancelled
Benchmarks of search for songs (push) / Run and upload benchmarks (push) Has been cancelled
Benchmarks of search for Wikipedia articles (push) / Run and upload benchmarks (push) Has been cancelled
5104: Bump xt0rted/pull-request-comment-branch from 2 to 3 r=curquiza a=dependabot[bot] Bumps [xt0rted/pull-request-comment-branch](https://github.com/xt0rted/pull-request-comment-branch) from 2 to 3. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/xt0rted/pull-request-comment-branch/releases">xt0rted/pull-request-comment-branch's releases</a>.</em></p> <blockquote> <h2>v3.0.0</h2> <ul> <li>Updated node runtime from 16 to 20</li> <li>Bumped <code>`@actions/core</code>` from 1.10.0 to 1.11.1</li> <li>Bumped <code>`@actions/github</code>` from 5.1.1 to 6.0.0</li> <li>Bumped <code>undici</code> from 5.28.3 to 5.28.4</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/xt0rted/pull-request-comment-branch/blob/main/CHANGELOG.md">xt0rted/pull-request-comment-branch's changelog</a>.</em></p> <blockquote> <h2><a href="https://github.com/xt0rted/pull-request-comment-branch/compare/v2.0.0...v3.0.0">3.0.0</a> - 2024-11-19</h2> <ul> <li>Updated node runtime from 16 to 20</li> <li>Bumped <code>`@actions/core</code>` from 1.10.0 to 1.11.1</li> <li>Bumped <code>`@actions/github</code>` from 5.1.1 to 6.0.0</li> <li>Bumped <code>undici</code> from 5.28.3 to 5.28.4</li> </ul> <h2><a href="https://github.com/xt0rted/pull-request-comment-branch/compare/v1.4.0...v2.0.0">2.0.0</a> - 2023-03-29</h2> <ul> <li>Updated node runtime from 12 to 16</li> <li>Removed deprecated <code>ref</code> and <code>sha</code> outputs. If you're using these then you should switch to <code>head_ref</code> and <code>head_sha</code> respectively.</li> </ul> <h2><a href="https://github.com/xt0rted/pull-request-comment-branch/compare/v1.3.0...v1.4.0">1.4.0</a> - 2022-10-23</h2> <ul> <li>Bumped <code>`@actions/core</code>` from 1.2.7 to 1.10.0</li> <li>Bumped <code>`@actions/github</code>` from 4.0.0 to 5.1.1</li> <li>Bumped <code>node-fetch</code> from 2.6.1 to 2.6.7</li> </ul> <h2><a href="https://github.com/xt0rted/pull-request-comment-branch/compare/v1.2.0...v1.3.0">1.3.0</a> - 2021-05-09</h2> <ul> <li>Bumped <code>`@actions/core</code>` from 1.2.5 to 1.2.7</li> <li>Updated the <code>repo_token</code> input so it defaults to <code>GITHUB_TOKEN</code>. If you're already using this value you can remove this setting from your workflow.</li> </ul> <h2><a href="https://github.com/xt0rted/pull-request-comment-branch/compare/v1.1.0...v1.2.0">1.2.0</a> - 2020-09-09</h2> <ul> <li>Deprecated <code>ref</code> and <code>sha</code> outputs in favor of <code>head_ref</code> and <code>head_sha</code>.</li> <li>Added <code>base_ref</code> and <code>base_sha</code> outputs</li> <li>Bumped <code>`@actions/core</code>` from 1.2.2 to 1.2.5</li> <li>Bumped <code>`@actions/github</code>` from 2.1.1 to 4.0.0</li> </ul> <h2><a href="https://github.com/xt0rted/pull-request-comment-branch/compare/v1.0.0...v1.1.0">1.1.0</a> - 2020-02-21</h2> <ul> <li>Bumped <code>`@actions/github</code>` from 2.1.0 to 2.1.1</li> </ul> <h2><a href="https://github.com/xt0rted/pull-request-comment-branch/releases/tag/v1.0.0">1.0.0</a> - 2020-02-09</h2> <ul> <li>Initial release</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|---|---|---|
| .cargo | ||
| .github | ||
| assets | ||
| crates | ||
| workloads | ||
| .dockerignore | ||
| .gitignore | ||
| .rustfmt.toml | ||
| BENCHMARKS.md | ||
| bors.toml | ||
| Cargo.lock | ||
| Cargo.toml | ||
| CODE_OF_CONDUCT.md | ||
| config.toml | ||
| CONTRIBUTING.md | ||
| Cross.toml | ||
| Dockerfile | ||
| download-latest.sh | ||
| LICENSE | ||
| PROFILING.md | ||
| README.md | ||
| rust-toolchain.toml | ||
| SECURITY.md | ||
Website | Roadmap | Meilisearch Cloud | Blog | Documentation | FAQ | Discord
⚡ A lightning-fast search engine that fits effortlessly into your apps, websites, and workflow 🔍
Meilisearch helps you shape a delightful search experience in a snap, offering features that work out of the box to speed up your workflow.
🖥 Examples
- Movies — An application to help you find streaming platforms to watch movies using hybrid search.
- Ecommerce — Ecommerce website using disjunctive facets, range and rating filtering, and pagination.
- Songs — Search through 47 million of songs.
- SaaS — Search for contacts, deals, and companies in this multi-tenant CRM application.
See the list of all our example apps in our demos repository.
✨ Features
- Hybrid search: Combine the best of both semantic & full-text search to get the most relevant results
- Search-as-you-type: Find & display results in less than 50 milliseconds to provide an intuitive experience
- Typo tolerance: get relevant matches even when queries contain typos and misspellings
- Filtering and faceted search: enhance your users' search experience with custom filters and build a faceted search interface in a few lines of code
- Sorting: sort results based on price, date, or pretty much anything else your users need
- Synonym support: configure synonyms to include more relevant content in your search results
- Geosearch: filter and sort documents based on geographic data
- Extensive language support: search datasets in any language, with optimized support for Chinese, Japanese, Hebrew, and languages using the Latin alphabet
- Security management: control which users can access what data with API keys that allow fine-grained permissions handling
- Multi-Tenancy: personalize search results for any number of application tenants
- Highly Customizable: customize Meilisearch to your specific needs or use our out-of-the-box and hassle-free presets
- RESTful API: integrate Meilisearch in your technical stack with our plugins and SDKs
- Easy to install, deploy, and maintain
📖 Documentation
You can consult Meilisearch's documentation at meilisearch.com/docs.
🚀 Getting started
For basic instructions on how to set up Meilisearch, add documents to an index, and search for documents, take a look at our documentation guide.
🌍 Supercharge your Meilisearch experience
Say goodbye to server deployment and manual updates with Meilisearch Cloud. Additional features include analytics & monitoring in many regions around the world. No credit card is required.
🧰 SDKs & integration tools
Install one of our SDKs in your project for seamless integration between Meilisearch and your favorite language or framework!
Take a look at the complete Meilisearch integration list.
⚙️ Advanced usage
Experienced users will want to keep our API Reference close at hand.
We also offer a wide range of dedicated guides to all Meilisearch features, such as filtering, sorting, geosearch, API keys, and tenant tokens.
Finally, for more in-depth information, refer to our articles explaining fundamental Meilisearch concepts such as documents and indexes.
📊 Telemetry
Meilisearch collects anonymized user data to help us improve our product. You can deactivate this whenever you want.
To request deletion of collected data, please write to us at privacy@meilisearch.com. Remember to include your Instance UID in the message, as this helps us quickly find and delete your data.
If you want to know more about the kind of data we collect and what we use it for, check the telemetry section of our documentation.
📫 Get in touch!
Meilisearch is a search engine created by Meili, a software development company headquartered in France and with team members all over the world. Want to know more about us? Check out our blog!
🗞 Subscribe to our newsletter if you don't want to miss any updates! We promise we won't clutter your mailbox: we only send one edition every two months.
💌 Want to make a suggestion or give feedback? Here are some of the channels where you can reach us:
- For feature requests, please visit our product repository
- Found a bug? Open an issue!
- Want to be part of our Discord community? Join us!
Thank you for your support!
👩💻 Contributing
Meilisearch is, and will always be, open-source! If you want to contribute to the project, please look at our contribution guidelines.
📦 Versioning
Meilisearch releases and their associated binaries are available on the project's releases page.
The binaries are versioned following SemVer conventions. To know more, read our versioning policy.
Differently from the binaries, crates in this repository are not currently available on crates.io and do not follow SemVer conventions.