# Meilisearch fulltext engine

**URL:** <https://help.nextcloud.com/t/meilisearch-fulltext-engine/239219>\
**Category:** 💻 Development\
**Tags:** feature\
**Created:** [January 24, 2026, 4:55am UTC](https://help.nextcloud.com/t/meilisearch-fulltext-engine/239219 "2026-01-24T04:55:31Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![NextClout](https://help.nextcloud.com/letter_avatar/nextclout/32/6_449c533f586939b6e5f246632a46421f.png) [@NextClout](https://help.nextcloud.com/u/NextClout)\
**Post date:** [January 24, 2026, 4:55am UTC](https://help.nextcloud.com/t/meilisearch-fulltext-engine/239219/1 "2026-01-24T04:55:31Z")

</div>

I have just converted existing Elastic Search app to Meilisearch.

> **[GitHub - ser/nextcloud\_fulltextsearch\_meilisearch: Meilisearch backend for NextCloud search](https://github.com/ser/nextcloud_fulltextsearch_meilisearch)**
>
> Meilisearch backend for NextCloud search

Please work on this software with me if you need it.

---

<div class="post-metadata">

**Author:** ![Rubilmax](https://help.nextcloud.com/user_avatar/help.nextcloud.com/rubilmax/32/77200_2.png) [@Rubilmax](https://help.nextcloud.com/u/Rubilmax)\
**Post date:** [February 28, 2026, 9:47pm UTC](https://help.nextcloud.com/t/meilisearch-fulltext-engine/239219/2 "2026-02-28T21:47:59Z")

</div>

I updated it: [GitHub - Rubilmax/fulltextsearch\_meilisearch: 🔍 Use Meilisearch to index the content of your Nextcloud](https://github.com/Rubilmax/fulltextsearch_meilisearch)

Working with nextcloud 33 and latest meilisearch

---

<div class="post-metadata">

**Author:** ![onurb](https://help.nextcloud.com/letter_avatar/onurb/32/6_449c533f586939b6e5f246632a46421f.png) [@onurb](https://help.nextcloud.com/u/onurb)\
**Post date:** [May 1, 2026, 10:11am UTC](https://help.nextcloud.com/t/meilisearch-fulltext-engine/239219/3 "2026-05-01T10:11:42Z")

</div>

this sounds great, like to try. But I cannot find the connector for nextcloud as described ([https://github.com/nextcloud/fulltextsearch\_meilisearch.git](https://github.com/nextcloud/fulltextsearch_meilisearch.git))

Where I’m wrong 🤔

---

<div class="post-metadata">

**Author:** ![NextClout](https://help.nextcloud.com/letter_avatar/nextclout/32/6_449c533f586939b6e5f246632a46421f.png) [@NextClout](https://help.nextcloud.com/u/NextClout)\
**Post date:** [May 1, 2026, 3:07pm UTC](https://help.nextcloud.com/t/meilisearch-fulltext-engine/239219/4 "2026-05-01T15:07:26Z")

</div>

you are not wrong, such an address does not exist.

---

<div class="post-metadata">

**Author:** ![onurb](https://help.nextcloud.com/letter_avatar/onurb/32/6_449c533f586939b6e5f246632a46421f.png) [@onurb](https://help.nextcloud.com/u/onurb)\
**Post date:** [May 2, 2026, 7:13am UTC](https://help.nextcloud.com/t/meilisearch-fulltext-engine/239219/5 "2026-05-02T07:13:00Z")

</div>

But this is mentioned in the post of Rubilmax. If there is no connector for meilisearch, I don’t understand how to use meilisearch for NC?

In any thing I think there is no practical use for it in NC AIO on Synology, because after every restart of the containers for the daily backup the fulltext search checkbox is unchecked because of the missing seccomp ☹

---

<div class="post-metadata">

**Author:** ![NextClout](https://help.nextcloud.com/letter_avatar/nextclout/32/6_449c533f586939b6e5f246632a46421f.png) [@NextClout](https://help.nextcloud.com/u/NextClout)\
**Post date:** [May 2, 2026, 9:03am UTC](https://help.nextcloud.com/t/meilisearch-fulltext-engine/239219/6 "2026-05-02T09:03:14Z")

</div>

You need to use the software from the top post. But I Have never tested it on Synology, though.

---

<div class="post-metadata">

**Author:** ![knedlyk](https://help.nextcloud.com/letter_avatar/knedlyk/32/6_449c533f586939b6e5f246632a46421f.png) [@knedlyk](https://help.nextcloud.com/u/knedlyk)\
**Post date:** [August 12, 2026, 6:16am UTC](https://help.nextcloud.com/t/meilisearch-fulltext-engine/239219/7 "2026-08-12T06:16:01Z")

</div>

I suggest to use tika for indexing office documents.
