A step by step guide to adding site search to your Nuxt ecommerce

We have just released our new version which development has been driven by our desire for simplicity of use.

We realized that some features were not easy to use because of design choices. The whole team gathered around the table and debated the API routes and their RESTfulness until everyone agreed on a proposal. We hope to strike a good balance between simplicity and customization.

So what is new in the v0.9?

*   Schema deletion!
*   Included web interface to try out your search
*   New settings handling
*   Simplified custom ranking rules
*   Added primary key
*   New built-in ranking rule names
*   Simplified authentication
*   Production and development mode
*   Bug fixes, syntax changes and, improvements

Schemaless
----------

The schemaless idea was in our mind for quite a while. When getting started, the user shouldn’t be required to specify how Meilisearch should handle every field, but only when their needs are really specific and out of the ordinary.  
Now, by default, Meilisearch will display every documents field, make them all searchable and will infer the document's primary key based on the provided documents structure.  
This solution causes way less friction when starting using Meilisearch.

Web interface
-------------

In the previous version, once you had started your Meilisearch engine and inserted some documents into it, the smooth experience stopped there. In order to try out the search, you had to either submit requests using curl or an SDK, either creating a front-end search bar connected to Meilisearch.

Now that a web interface is shipped with Meilisearch, all you need to do is open your web browser and enter Meilisearch’s address to visit it locally. This will lead you to a web page with a search bar that will allow you to search in a selected index.

![movies_web_2-1](https://unable-actionable-car.media.strapiapp.com/movies_web_2_1_f8a769507a.gif)

Since the production environment requires an API-key for searching, the web interface is only available in development mode.

Settings
--------

Anything that isn’t necessary to make your Meilisearch instance up and running can now be configured in the settings.

For each setting there is a route, thus making it possible to only update a specific setting. The global setting route gives you the possibility to post a configuration file describing your customizations, which will facilitate the creation of similar Meilisearch instances based on the same settings.

#### Example

```json
{
  "rankingRules": [
      "typo",
      "words",
      "proximity",
      "attribute",
      "wordsPosition",
      "exactness",
      "desc(release_date)"
  ],
  "distinctAttribute": null,
  "searchableAttributes": [
      "title",
      "description",
      "uid"
  ],
  "displayedAttributes": [
      "title",
      "description",
      "release_date",
      "rank",
      "poster"
  ],
  "stopWords": null,
  "synonyms": {
      "wolverine": ["xmen", "logan"],
      "logan": ["wolverine", "xmen"]
  },
  "indexNewFields": false
}

```

[All the settings can be found here](https://docs.meilisearch.com/reference/api/settings.html)

Simplified custom ranking rules
-------------------------------

In the previous version, creating your own rules could be confusing. We simplified this task! All you have to do now is add an ascending (`asc()`) or descending (`desc()`) rule on one of your fields in the ranking rules list.

```json
 "rankingRules": [
      "typo",
      "words",
      "proximity",
      "attribute",
      "wordsPosition",
      "exactness",
      "desc(release_date)"
  ]

```

If you update your ranking rules following this example, you will note that your changes have been taken into account by Meilisearch immediately. This means that once all the other rules have been applied, Meilisearch will consider documents with more recent release\_date's more relevant than older ones.

Primary key
-----------

Meilisearch will try to infer the primary key from the documents you upload. This inference will search for the first field containing the string `id` in its attribute.  
Sometimes, it may happen that no key can be found. In such a case, Meilisearch is not able to infer it.

Since Meilisearch needs a primary key to store the documents, if the latter cannot be inferred, we have set up two alternative ways to communicate the primary key to Meilisearch.

*   By giving it on index creation :

```json
{
  "uid": "movies",
  "primaryKey": "movieUniqueName"
}
```
    
*   By giving it on document addition

```bash
curl -X POST 'http://localhost:7700/indexes/movies/documents?primaryKey=movieUniqueName' --data @movies.json
```



New ranking rules names
-----------------------

In the previous versions, ranking rules names were too long and could contain unnecessary special characters. From now on, they have been simplified. Here is the list of the new built-in ranking rules:

*   `typo`
*   `words`
*   `proximity`
*   `attribute`
*   `wordsPosition`
*   `exactness`

[Follow this guide to know more about what each ranking rules does](https://docs.meilisearch.com/learn/core_concepts/relevancy.html).

Simplified authentication
-------------------------

When adding a master key to Meilisearch, a private key and a public key are generated on launch.  
The public key only grants permission to the routes that execute searches and get documents.  
The private key grants access to every other route in Meilisearch except for the `GET /keys` route. As it returns both the public and private keys, this route is accessible only with the master key.

[Read this to learn more about authentication in Meilisearch](https://docs.meilisearch.com/reference/features/authentication.html).

Production and development mode
-------------------------------

When launching your Meilisearch instance, setting the environment is now available as an option.  
By default, the environment is set to development mode.

While in development mode, you don't have to provide a master key. In that case, every route is accessible without requiring any API key. You are also able to **access the web interface**.

While in production mode, if no master key is given, the instance will be considered unsafe for production and will not start.

Bug fixes, syntax changes, and improvements
-------------------------------------------

*   Removed dead-lock in the update system
*   Settings can be added even when no primary key is known
*   `POST /documents/delete` changed to `POST /documents/delete-batch`
*   Speed up the reindexing system
*   When no highlight is prompted during search there will be no `_highlighted` field in the returned documents
*   Removed `searchableAttributes` from the search query parameters.
*   To know the stats of an index the route is now: `GET /indexes/:index_uid/stats` and not `GET /stats/:index_uid`
*   Documents ids' can only contain the following characters: `A-Z a-z 0-9`, `-`, and `_`

Some adjustments on routes’ design we made are temporary choices we took in order to release a working version. The `/key` route, for example, although functional, is too simple and not tailored to developers’ common needs. We are currently thinking about how to handle it better, and we are open to any advice!

This version took us about three months to finish, taking into account that the v0.8.5 has not been officially released but added to the v0.9 release. We did a lot of work on process organization to ensure that everything would be ready at the same time: the core Meilisearch, the documentation, and the SDK.

We are thrilled about how these latest changes will improve the users' experience with Meilisearch. This release is the result of a lot of discussions among our contributors and us. We are eager to hear about your experience with Meilisearch. Any suggestion or feedback is more than welcome since those are the premises of a long-term and ambitious project that will be built upon the decisions we make today.

![](https://unable-actionable-car.media.strapiapp.com/o_Ipwxee_S_Py1cnw_Ypq_J1w_Dufer_Collateral_test_0ac313d3ae.jpg)

Meilisearch v0.9: What’s new?

This year, we’ve launched Meilisearch's very first contributors program: the Meilistars. The aim of a contributors’ program is to gather top community contributors and foster our relationship, highlight the fantastic work they produce, and maybe even help create connections. We won’t go much in-depth on this topic at the moment as we’re hoping to share more in a dedicated blog post, so watch this space!  
  
As an initiative to bring the spotlight to our amazing community members, we’ve asked if they would be interested in participating in a series of interviews so that we can get to know them better.  
  
And we’re kick-starting our interviews with Minoru Osuka. You may have already met him on GitHub as [Mosuka](https://github.com/mosuka) or on Twitter as [@minoru\_osuka](https://twitter.com/minoru_osuka).

Let’s hear all together a bit more from him!

Meet Minoru
===========

First things first, we’ve asked him to introduce himself in his own words!

> “I'm Minoru Osuka. I work as a software engineer and tech lead for a company that provides a job search engine in Japan. I'm mainly involved in search platform development. My hobby is software development, and I've released some of the software I developed as OSS on GitHub.”

So not only does Minoru work in tech, but he also considers it his hobby! We were very curious to know how he got into the tech field.

Minoru explains that he started in a technical school as a programming instructor, but he wished to increase his practical experience and decided to join a software development company.

> “This was the start of my career as a software developer. As I used search engines in my work, I became interested in how they work, so I moved to an Internet portal site and have worked in the search engine field ever since.”

Minoru + Meiliseach: it was meant to be
=======================================

Hearing that Minoru actually worked with search engines, we couldn’t help but ask when he heard about Meilisearch and how he started using it.

> “It was about May 2022 when Meilisearch started supporting the Japanese language. Meilisearch used the Japanese morphological analyzer [Lindera](https://github.com/lindera-morphology/lindera) as their Japanese tokenizer. I maintain Lindera, so it was a very fortunate event.”

Minoru is very grateful to [Kination](https://github.com/kination) and [Miiton](https://github.com/miiton), who respectively created the [first pull request](https://github.com/meilisearch/charabia/pull/70) to add Japanese language support in Meilisearch and implemented it. It is thanks to their combined work that the Japanese support of Meilisearch has become what it is today.

> “I have yet to actually use Meilisearch in my work, but [voluntas](https://github.com/voluntas) introduced [a case study using Meilisearch](https://zenn.dev/voluntas/scraps/77ae77d06deadc) for their Japanese document search service, which attracted a lot of attention.”

Open source to the bone
=======================

Minoru's frequent references to other members of the Meilisearch community during the interview were too significant to overlook. He expressed great satisfaction at having had the opportunity to connect with fellow community members.

> “Ever since Meilisearch adopted Lindera, my Twitter followers have increased. I am happy to have met them. I'm very grateful to Meilisearch.”

It's truly remarkable how deeply involved Minoru is in the open-source community. In addition to contributing to Meilisearch and maintaining Lindera, he has also built his own [distributed search server](https://github.com/mosuka/bayard).

> “I had been using Elasticsearch and Solr for a long time, but using them was not enough for me, so I decided to build a distributed search server while also learning Rust. It was tough, but I learned a lot.”

Oddly, it was this project that led him to maintain Lindera:

> “I started working on Lindera because I developed a distributed search server on my own. \[...\] My friend, who is developing a full-text search library, also developed a Japanese morphological analyzer, but it was not registered on [crates.io](https://crates.io/). When I contacted him to see if he would register it on crates.io, he gave me a surprising answer: ‘I want you to take over this project.’ I was also interested in morphological analyzers, so I decided to take over the development.”

Minoru also thanked [fulmicoton](https://github.com/fulmicoton), the developer of [kuromoji-rs](https://github.com/fulmicoton/kuromoji-rs), the original software that eventually evolved into Lindera, describing it as “a wonderful OSS.”

A vision for the future
=======================

Given his extensive contributions, it's no surprise that Minoru knows Meilisearch inside out. Its immediate usability is what Minoru values most about it. In fact, he particularly values a specific feature that contributes to this accessibility.

> “Meilisearch's automatic detection of what language the indexed documents are written in is great. This is a very helpful feature for users unfamiliar with search engines.”

During our conversation with Minoru, we couldn't pass up the chance to ask him about any improvements he'd like to see in Meilisearch's near future. Unsurprisingly, his suggestions focused on language support. Specifically, he suggested implementing a mechanism to normalize characters **before** they are tokenized.

For those unfamiliar with the process, it currently happens the other way around. A text is tokenized—segmented into words—and then, each word is normalized based on language particularities. For a romance language like French, this process includes lowercasing and removing diacritical marks such as accents or anything that doesn’t impact the meaning of the text. To those interested in the subject, you can join the discussion on [GitHub](https://github.com/meilisearch/product/discussions/532#discussioncomment-3812425) or [read more](/blog/improving-meilisearchs-language-support/)bout how we handle language support.

Minoru's suggestions for language support included customizing the normalizer for each field. Suppose there is a document with an address field, and he would like to be able to instruct Meilisearch to convert the Kanji numbers in the address field into Arabic numbers. In his words:

> "Right now, Meilisearch does not have a normalizer for Japanese, but it would be nice to be able to customize it for each field \[…\] I would also like to contribute to Japanese normalizers."

We look forward to working on improving our language support with Minoru, and any language aficionados that would want to support our efforts!

It was a real pleasure talking with Minoru, getting to know him better, and understanding his insight on Meilisearch, his usage, and the people he managed to meet through it.

As a reminder, you can find [Minoru on GitHub](https://github.com/mosuka) or contribute to [Lindera](https://github.com/lindera-morphology/lindera).  
We hope you found this interview as interesting as we did and look forward to meeting all of our incredible Meilistars.

Minoru Osuka: POV of a main language contributor

<Callout>
  Due to the recent documentation site migration, our documentation doesn't currently use Vale. You can still view our style guide on [GitHub](https://github.com/meilisearch/documentation/tree/b6837449f09587f9d6df92e1eea0c44cc394f398/.vale/styles/Meilisearch).
</Callout>

Writing is a time-consuming process. Depending on the writer and the review process, it can take a while to get content ready for publication. Whether you’re a solo writer or a big team, prose linters can help ensure a consistent tone and style.  

Similar to code linters, prose linters automatically check your text for errors. Unlike grammar checkers, which highlight violations of grammatical rules, prose linters focus on how you can make your text better by addressing common usage problems like extra spaces, repeated words, excessive use of jargon, sexist language, and incorrect capitalization.  

Prose linters can also provide a framework for creating and enforcing an [editorial style guide](https://www.writethedocs.org/guide/writing/style-guides/). This helps with the review process as you can now focus on reviewing the content itself instead of pointing out typos and preferred usage patterns. This is particularly important when working in open-source projects like Meilisearch, where you have many contributors unfamiliar with your style guide.  

What is Vale?
-------------

[Vale](https://vale.sh/docs/vale-cli/overview/) is an open-source, highly customizable, syntax-aware prose linter. It supports documents written in many different formats such as Markdown, HTML, reStructuredText, AsciiDoc, DITA, and XML.  

Vale isn’t your only option when it comes to prose linting. There are many other open-source tools available, including [proselint](http://proselint.com/), [textlint](https://textlint.github.io/), and [alex](https://alexjs.com/).  

At Meilisearch, we decided to go with Vale because it’s fast, easy to set up, flexible, and comes with existing rules to help you get started.

Where do I start?
-----------------

Though it may seem daunting, setting up Vale can be fairly straightforward if you start small and keep things simple. In this post, we’ll go over how to use Vale in a project much like [Meilisearch’s documentation](https://github.com/meilisearch/documentation).

### Step 1: Style guide

The first step is to create a style guide. A style guide ensures a consistent tone and style regardless of how big your team gets. It establishes standard practices when people may have different opinions, such as whether or not to use the oxford comma.  

If you don’t have an in-house style guide, you can check out [Google’s](https://developers.google.com/style) or [Microsoft’s](https://learn.microsoft.com/en-us/style-guide/welcome/) to help you get started. Over time you will memorize most of the rules, but it’s possible to overlook mistakes and sometimes forget the rules altogether. We’re only human.  

And that is where Vale comes in. It allows you to “codify” a style guide and checks your text against all the rules in that style guide. If it detects any issues, it displays suggestions, warnings, or errors on the console.

![](https://lh4.googleusercontent.com/jqa7GUDjATPh8UaNybvMrcuCURAdHu1mMrrm_M6T9MdKq_M3CPf0i8Gs60_yEt08zZGrCd43ZxsrdRDQ3nP8EBEXitjEeqFdDHYlD6HZ19CcGhkvpHHlR6NwZxbjkOMl6IpzUR1RCJ9P6myZoEHIOhs)

### Step 2: Install Vale

I’m using macOS and ran `brew install vale` in my console to install Vale.

If you’re using a different operating system, check out Vale’s documentation for [installation instructions](https://vale.sh/docs/vale-cli/installation/).  

Verify the installation by typing  `vale -v` in your console. If this command returns Vale’s version number, the installation was successful.  

Finally, create the following files and folders:

```json
├── .vale.ini
│   ├──  styles
│   │	    ├── Style guide
│   │       └── Vocab
```

### Step 3: Configuring Vale - vale.ini

Create a `vale.ini` file at the root of your repository. This is the Vale configuration file where you define what you want Vale to do and what files to lint. Let’s start with a basic setup—you can always add to it later based on your project’s needs.

```json
StylesPath = .vale/styles
MinAlertLevel = suggestion

Vocab = word_list

[*.md]
BasedOnStyles = Meilisearch
```

*   `StylesPath` is where Vale looks for your style guide (more on that in the next step). The path can be relative or absolute to the location of the `vale.ini` file.  
    
*   `MinAlertLevel` specifies the minimum alert level that Vale will report. By default, it’s set to `warning`. The other options are `error`  and `suggestion`.  
    An error indicates you did something wrong, like using extra spaces or making a typo. A warning isn’t as severe as an error, but indicates something you should avoid, like making sure your sentences don’t become too long. A suggestion is a recommendation to do something that is usually—but not always—a good idea, like breaking your sentence into two instead of using a semicolon.  
    If a rule is set to `suggestion`, you will see suggestions, warnings, and errors. If it is set to `warning`, Vale will only show errors and warnings, no suggestions.  
    
*   `Vocab`: This is where you create a directory containing the `accept.txt` and `reject.txt` files. Both files accept words, phrases, and [regular expressions](https://ubuntu.com/blog/regex-basics). If your text contains words that do not exist in the dictionary (e.g. “Meilisearch”), you can add them to `accept.txt` and Vale won’t angrily scream at you for making a “typo”. Vale will flag all occurrences listed in `reject.txt` as errors. This can be useful when you want writers to avoid a specific word—if you are writing about search engines and databases, for example, using “indexation” can be confusing.  
    
*   `[*.md]` tells Vale to only lint markdown files. If you want to lint plain text files, use `[*.txt]`.  
    
*   `BasedOnStyles` specifies the style guide Vale should use for linting.  
    

You can specify other settings, including what tokens and HTML tags to ignore and what Vale should consider an individual word. You can read more about the `vale. ini` file in [Vale’s documentation](https://vale.sh/docs/topics/config/).

### Step 4: Rules and the styles folder

As I mentioned earlier, you need a style guide to use Vale. You then convert this style guide into something Vale can understand: rules.

Rules use different [extension points](https://vale.sh/docs/topics/styles) to perform specific tasks. For example, the `existence` extension point looks for the existence of a particular token, `repetition` looks for repeated tokens, `spelling` implements spell checking, and so on. In Vale, each rule is a YAML file. The `styles` folder contains the individual rules that make up the style guide.  

If you don’t want to create your own style guide or need a starting point to build from, Vale comes with ready-to-use style guides that you can apply to your docs and start linting. Here are some style guides that helped us get started:

*   [Google](https://github.com/errata-ai/Google)
*   [GitLab](https://gitlab.com/gitlab-org/gitlab/-/tree/master/doc/.vale/gitlab)
*   [RedHat](https://github.com/redhat-documentation/vale-at-red-hat/tree/main/.vale/styles/RedHat)

You can find more on [Vale’s GitHub](https://github.com/errata-ai/packages) repository.  

Let’s start with a rule for sentence length. Your style would say something like “Ensure sentences don’t exceed 40 words”. This is what the rule looks like as a YAML file:

```json
# Warning: Meilisearch.SentenceLength

# Counts words in a sentence and alerts if a sentence exceeds 40 words.

extends: occurrence
message: 'Shorter sentences improve readability (max 40 words).'
scope: sentence
link: https://docs.gitlab.com/ee/development/documentation/styleguide/index.html#language
level: warning
max: 40
token: \b(\w+)\b
```

This rule counts the words in a sentence and throws a warning if it exceeds 40 words. The `scope` is set to `sentence`: this ensures that Vale does not apply this rule to other parts of the text, like headings or tables.  

The `level` is set to `warning`. Written text is complicated, and Vale will find false positives. There are no sure-fire ways of deciding when a rule should be a suggestion, warning, or an error. You will need to make decisions and learn as you go.  

I suggest reviewing your rules over time to update and, in some cases, delete outdated rules. Initially, the Meilisearch docs didn’t have a rule on sentence length. When we added it, the maximum length of a sentence was 45. Now it’s 40, and we plan on bringing it down to 35.  

You can also enable or disable specific rules within a style guide by adding them to `vale.ini`:  

```json
Meilisearch.Headings = NO
Meilisearch.Spelling = NO
Meilisearch.Semicolons = NO
```

The above lines disable the Heading, Spelling, and Semicolons rules from the [Meilisearch style guide](https://github.com/meilisearch/documentation/tree/main/.vale/styles).  

### Step 5: Run Vale

Now, when you use the following command on your console to lint your whole project:  

```json
vale .
```

Vale will check all your files against the rules stored in `BasedOnStyles`. If Vale detects any issues, it will display suggestions, warnings, and errors on the console.  

You can also lint individual files using:  

```json
vale {file_path} 
```

### Step 6: Automate Vale checks

All the checks we’ve discussed so far are for your local files. Once you’re confident the rules work as intended, you can automate these checks using the [Vale GitHub action](https://github.com/errata-ai/vale-action)! At the Meilisearch documentation repository, we configured it to run for every pull request. As mentioned before, Vale may find false positives. Since you don’t want a PR blocked because Vale isn’t working as it should, I recommend starting with a few rules, and slowly tweaking them to avoid failing checks.  

### Conclusion

That is all, folks! I hope I was able to help you get started with Vale (and a style guide). This was a quick overview to introduce you to Vale’s features. Tweaking it to your needs takes time and many, _many_ iterations.  

![](https://lh4.googleusercontent.com/zp5NecwV9Bc8pMsSf2QeV8yOMMGWoJR8bENrOuQNNFWat7J0KtzDq1n9oBrEW1lKgJO8utxivJS9UqXuMutCmft2o8x3LIE3bUIQFuqcCTkgQ6H5y6hzVAEXgEPYkGHlwnTZnaJ3r3rEq4LyWGFYOVU)

Once configured, Vale can automate parts of the review process and allow you to focus on the parts of a text that computers are not very good at. At least not yet.  

Oh, and if you’re curious, check out [our style guide on GitHub](https://github.com/meilisearch/documentation/tree/main/.vale/styles) to see how we use Vale!

Prose linting with Vale

A few weeks ago we spoke to [Guillaume Mourier](/blog/author/gmourier/ about [the product manager’s role in the release of Meilisearch v1.0](/blog/planning-v1-and-beyond/ But what is a product manager, actually? What is his role in Meilisearch? We decided to go after him and shed some light on this mysterious (but extremely important) job.

![](https://media.tenor.com/WqrGt08ogFwAAAAC/scooby-doo-mystery-machine.gif)

What is a product manager?
==========================

Guillaume says the product manager is a key role in software development and can be divided into three main tasks.

First, product managers need to understand how people use a product: what makes their lives easier, what makes their lives harder, what they want to do but can’t because the product lacks a specific feature.

Second, they need to define a strategic vision of the product’s future so development is coherent and efficient. In Meilisearch’s case, this fundamental step means Guillaume works very closely with Quentin, our CEO.

Third, based on the product’s strategic vision and user feedback, product managers decide what features to implement with the resources they have at hand.

Guillaume tells us it’s a difficult balancing act. Sometimes our choices do not please everyone. Sometimes we don’t prioritize popular requests because we believe they do not align with our strategic vision.

The good news is this is done hand in hand with our community. Guillaume first analyzes topics discussed on [GitHub](https://github.com/meilisearch), as well as issues raised with our support team in our [Discord server.](https://discord.gg/meilisearch) Then, he comes up with solutions to the problems the users described, and plans when they should be done. As you can imagine, this is made much easier by the fact Meilisearch is open source.

How did you become Meilisearch’s Product Manager?
=================================================

![](https://media.tenor.com/fiBaWJK3vQQAAAAC/how-did-this-happen-david-rose.gif)

None of this is enough to scare Guillaume. Though he had experience as a backend developer, his transition into product management was, in a way, rather natural.

First of all, he tells us, he was interested not only in writing code and shipping new features, but knowing how his work impacted others. Did users actually adopt the feature he spent weeks carefully implementing and debugging? What did they like about it? What did they hate about it? He had no way of answering these questions. For him, it was like marching forward with his eyes closed—and without a map.

Rather than seeing his former job as a different career he closed the door on, Guillaume is very grateful for his technical knowledge. It gives him valuable insight in the technical challenges developers might have when implementing a feature, as well as some measure of empathy with Meilisearch’s users. He knows first-hand how good it feels to use a well designed product.

Does the product manager work alone?
====================================

One thing Guillaume is particularly proud of is having integrated product squads in Meilisearch’s development process. These working groups include one member from each team and meet periodically to discuss a feature, bringing to the table insights, needs, and challenges a proposed change might entail for their department.

Prior to the creation of the squads, Guillaume observed that a single team would make unilateral development decisions and begin implementation almost immediately. However, as other teams caught up, they would point out problems with the initial decision. Fixing these often required reworking fundamental aspects of the implementation very late in the process, which was risky, inefficient, and sometimes frustrating for everyone involved.

Product squads made it easier to establish smooth communication between teams and resulted in clearer processes leading to better and solid solutions.

What are the most and least appealing aspects of your job?
==========================================================

![](https://media.tenor.com/2iXnRerU6XkAAAAC/i-wanted-to-be-clear-on-the-pros-and-cons-to-be-real.gif)

One of the best experiences for Guillaume is seeing how new features improve the lives of Meilisearch’s users, making their jobs easier and more pleasant.  
  
He confesses that being Product Manager isn’t your usual 9 to 5 that you can simply forget about when you clock out. He has spent more than a few evenings thinking about a particular insightful piece of negative user feedback or features being worked on at that moment. One must be truly passionate to be a product manager!

What features are you the happiest about?
=========================================

Out-of-the-box support for nested fields is one feature Guillaume is particularly satisfied with, especially because of the incredible amount of positive feedback. Sorting, which Meilisearch only implemented in 2021, had a similarly powerful impact for many users.

Multi-tenancy using tenant tokens is another personal favorite. He thinks the implementation is still not there and will certainly be polished in the near future, but it has nevertheless been a huge help for users working with complex applications and sensitive data.

What about the evolution of the product manager’s role?
=======================================================

Guillaume doesn’t truly belong to only one team within Meilisearch. This autonomy allows him to be involved with other teams and build bridges between projects and initiatives.

That said, he spends a considerable amount of time with the engine team. Right now this is good and necessary, but he would like to eventually take a step away from the search engine and look at the broader context of Meilisearch. For example, how can he help the many users of our SDKs and plugins? It’s a difference not so much in the things a product manager does, but in their scope and the potential reach of his actions.

* * *

That was an interesting peek into all the planning that goes inside Meilisearch, wasn’t it? A big thanks to Guillaume for his time. Stay tuned for more interviews with our lovely colleagues. Want to know more about a specific task, team, or internal process? Tell us all about it on our public [Discord](https://discord.gg/meilisearch) server!

Balancing business, technology, and user experience

Winter was foretold. Now winter has come. In the Northern Hemisphere, it’s currently cold, gray, and the world news is as wintry as it gets.

“But at least,” said one of our team members, “thanks to remote work, I have _no_ dry skin!” At which point they proceeded to sympathize with all those poor people who had to work from the office, wash their hands with subpar soap 10 times a day, and end up with mummified hands, micro-cuts, and a snubbed cat that didn’t like being pet by such coarse hands.

Now, this is one silver lining to remote work that I had never considered before. It could very well be made into a viral parody video, but instead, I immediately added it to the long list of why we love remote work at Meilisearch.

**Make your own work environment**
==================================

Like many companies, we occasionally dabbled in remote work—and had to embrace it on a permanent basis during the Covid-19 lockdowns. Offering full remote work to all our team members is now an integral part of Meilisearch. We believe it's the best chance workers have to grind the daily grind to the ground.

Remote work doesn’t necessarily mean working from home, though. Some of us love it, but others like the energy of a shared place or enjoy a change of scene. (At least that's what they say. Personally, I'm convinced they enjoy the proximity of restaurants with fantastic takeaway for their lunch break.)

We still have an office in Paris, France. We have a small squad of 10 people close enough to come regularly. The rest of us can count on a 500 EUR monthly stipend dedicated to coworking spaces, cafés, or other shared places.

This flexibility suits us as it allows each person to work in their preferred environment. We never have heated disputes with our colleagues about whether or not a draft means a soar throat or a pleasant breeze. It’s possible to work in a very calm or very animated environment, fidget all day or listen to music without headphones. Flexible remote work makes for the most inclusive work environment; everyone can personalize their experience based on their needs.

Of course, we need our team to have a good setup. We follow a basic rule: each team member must have a desk, a chair, an external screen, and headphones. If they're already equipped or have any stipend left, they can select any other items! Team members receive their computers at their own addresses before their contract starts.

We haven't found a solution for people who can’t work without seeing their peers physically yet—and probably never will! Working with a team of remote people is a different experience. We try to be as transparent as possible during the hiring process so that people have a good idea of what to expect and prevent any disappointment.

**The infamous work-life balance**
==================================

Remote work is also a great equalizer of work-life balance. Weather doesn't have to be weathered, and traffic or crowded undergrounds don't have to be endured. As it gives more flexibility, our team members can save time and stress.

If a 5-10 minute pause is about turning on the washing machine, then all the better! It doesn’t take anything from us and can lift some mental load. We try to facilitate access to sports and [mental health support](/blog/our-first-steps-to-support-the-mental-health-of-our-team-members/)ome of our team members are running uphill first thing in the morning without us lifting a finger to support them though, so we can't begin to take the credit for all their activities!

An inherent risk of remote work is putting too much pressure on employees. As a French company, we are particularly careful about protecting their right to disconnect. We implemented [the 4-day workweek](/blog/how-we-implemented-the-4-day-work-week/)o emphasize this point. We are still looking into ways to help our team members create a good space for themselves. We are currently looking into child-care benefits for the parents in our midst. There may be other benefits that haven’t occurred to us yet—we are always on the lookout!

When speaking with companies opposed to remote work, we are sometimes asked how we ensure our team is _actually_ working. Well, we believe it's considerably easier to fake working in an office than remotely. At the end of the week, if the work is not done, no amount of "but I was online" is going to help. If managers in your company need to physically see someone in an office to be sure they're working, it puts the value on [presence](https://blog.dropbox.com/topics/work-culture/job-performance-isn-t-about-showing-up-anymore-and-that-s-a-good) rather than productivity. We believe people can be trusted until proven otherwise, rather than the contrary.

**The world is your oyster**
============================

We started by eliminating the constraint of only hiring people that live in the same city. As an open-source company, we’ve always been very proud to work with contributors from many different countries, and it only seemed logical to continue doing so with our team members. This meant we had to [adapt our salary grid to be more attractive worldwide](/blog/our-approach-to-salaries/)nd we continue to observe the market.

It also means our team members are not tied to a city and can move permanently to the countryside or a more attractive town with fewer job opportunities. Some of us use remote work to travel—working during the day and visiting the rest of the time.

We are not [an asynchronous team](https://about.gitlab.com/company/culture/all-remote/non-linear-workday/) yet. While we don’t need to have perfect overlap between team members, we need at least a half-day in which we can hold meetings or discuss issues. This still deprives us of applicants from opposite time zones, but this may change as we grow.

It’s important to us to maintain a strong team spirit among all coworkers. We've written before about how [we handle informal discussions in the workplace](/blog/how-we-create-space-for-casual-conversation-within-our-remote-team/)he future of our office is in question: though it’s a perfect go-to space for people in the area, it does create a different experience depending on where our employees are based. We may decide to close it entirely in the future!

As our offsite gets closer, we're excited to meet and chat IRL with our colleagues. This doesn’t mean, in our opinion, that it’s a bad thing to be working remotely—rather that our system is working really well if people are eager to come to these outings (for some of us, this means a 15 hours journey!).

* * *

We still have a lot of exciting adjustments to make: launch a complete company survey on the changes we could make, refine our asynchronous processes, and keep on our toes regarding our team-building activities. The list goes on!

I have to be honest with you: though I work from home, I still need to use hand cream in the winter. So maybe remote work doesn’t magic away _all_ the problems of the world… but the door it opens leads to a new spring for work. Remote work is a significant social progress for workers when implemented well, and we believe it is the future.

Remote work is the future of work

The release day of Meilisearch v1 has come and gone. [We presented the major changes in our latest version](/blog/whats-new-in-v1-0/)nd [we spoke at length about all the features you get when you use Meilisearch](/blog/v1-enterprise-ready-stable/)oday we give the spotlight to [Guillaume Mourier](/blog/author/gmourier/)ur Product Manager.

Guillaume’s role is strategic in nature, and that comes with the privilege of having a very good idea about Meilisearch’s future, and how we plan to reach our destination.

Planning Meilisearch’s first stable release
===========================================

The process for v1 was a bit different compared to the past. This time, Guillaume tells us, the focus was not on including new features or even fixing major issues, but rather on the stability of the product and its API. He believes developers and businesses must have a predictable and stable product—they need to know they can depend on Meilisearch for their daily work. Our ever growing user-base also pointed towards this need. More and more people have grown to rely on our product, and it is our responsibility to not disappoint them.

Because of that, Guillaume planned 2022 as a year heavily focused on stabilization and performance optimization. To give our users the reliability they needed, we had to stop making changes that required programmers altering their workflows or reworking parts of their application. The first step was revising the API so it remained easy to use while serving as a solid and flexible base for new features. The second was adding more fundamental functionality. And the last, but certainly not the least important, was to find ways of improving performance and stabilizing the command-line interface.

Now these strong foundations have been implemented, Guillaume is very excited to start planning and implementing new features. It is time to move into a new era.

![](https://unable-actionable-car.media.strapiapp.com/balanced_rocks_a98f5966b7.jpg)

It’s the little things that matter
==================================

Now v1 is online, Guillaume wants to iron out a longer-term roadmap—there are quite a lot of ideas already, but in Meilisearch’s new development phase we need to be more careful. Users will certainly be more vigilant and demanding as they follow our next steps. 

In terms of new features, Guillaume has his sights on a few quality of life improvements.

First of all, he wants to focus on bringing multi-index search to Meilisearch. This much-requested feature would make it easier to create unified search experiences in applications pooling data from many different indexes. This is also sort of a pet project of his: multi-index search has been in the works for some time and it was with a heavy heart he deprioritized it in 2022. 

Multi-index search will be released in incremental iterations. A first iteration will make it possible to send multiple search queries in a single HTTP call. This lays down the foundation for the following step: to release a new iteration that natively aggregates search results from different indexes into a single list.

Another area ripe for incremental improvements is Meilisearch's faceted search, which could be much simpler and more intuitive. For example, it is not possible today to sort facet values by the number of matched documents or their name. It is also impossible to search among the facet values themselves. Guillaume is enthusiastic about finding solutions to these problems—he assures us both things will soon be possible with Meilisearch.

![](/blog/content/images/2023/02/gestion-planning-cabinet-expertise-comptable.webp

Planning and pacing
===================

As the Product Manager, Guillaume needs to think not only about new features, but about Meilisearch’s development process. He believes our current product development cycle is too short, which means we tend to be trapped in a constant rush, running from release to release without enough time to properly think everything through. 

He’s very excited with the chance releasing v1 gives him: being able to plan things better, trial more features with users for a longer period of time, and reflect more on the valuable feedback our community gives us. Taking the time for all that enables us to start working more efficiently and prepare things much earlier.

What about semantic and AI-powered search?
==========================================

Recently, there has been widespread hype in the field of semantic search and natural language processing. Guillaume says it's an area we're following closely. Though these ideas might be very exciting, it is definitely challenging to provide contextualized and personalized search to end users while maintaining excellent performance and keeping Meilisearch a tool developers love to use. 

In the future, Meilisearch could evolve to a hybrid search service, uniting the best of both worlds. For now, however, we are focused on continuing to build upon the solid foundation we have created with v1.0.

—

We hope that piqued your interest—if so, stay tuned for more information on the future of search! 

  
Remember, you can get started with Meilisearch v1 in just a few minutes—everything works out of the box, no configuration required. Want more? We also have a handy [Quick Start guide on our documentation website](https://docs.meilisearch.com/learn/getting_started/quick_start.html).

Planning v1 and beyond

After three years of hard work and dedication, we are thrilled to announce **the launch of Meilisearch 1.0**. With this release, Meilisearch has taken a stride forward in its mission to help developers create fast, powerful, and reliable search experiences.

With more than 32,000 GitHub stargazers and 100,000 launches per month, Meilisearch is already well-loved by its community. Now, after countless hours spent polishing the API and architecture to perfection, we are confident and happy to release the first completely stable version of Meilisearch, with guaranteed compatibility through future versions.

Creating a seamless search experience for your users can be a daunting task, but it is crucial to help your business **elevate user satisfaction, drive conversions, and increase retention**. Enter **Meilisearch v1**: the most performant search engine on the market with zero setup required.

What is Meilisearch?
====================

**Meilisearch is an open-source, user-focused search engine** that easily integrates with any website or application. It features powerful built-in capabilities such as [search-as-you-type](https://docs.meilisearch.com/learn/what_is_meilisearch/features.html?utm_source=release-post&utm_id=v1-announcement&utm_content=search-as-you-type#search-as-you-type), [typo tolerance](https://docs.meilisearch.com/learn/what_is_meilisearch/features.html?utm_source=release-post&utm_id=v1-announcement&utm_content=typo-tolerant#typo-tolerant), [faceted search](https://docs.meilisearch.com/learn/what_is_meilisearch/features.html?utm_source=release-post&utm_id=v1-announcement&utm_content=faceted-search#faceting), [geo search](https://docs.meilisearch.com/learn/advanced/geosearch.html?utm_source=release-post&utm_id=v1-announcement&utm_content=geosearch), and [multi-tenancy](https://docs.meilisearch.com/learn/security/tenant_tokens.html?utm_source=release-post&utm_id=v1-announcement&utm_content=multitenancy). A suite of [SDKs and libraries](https://docs.meilisearch.com/learn/what_is_meilisearch/sdks.html?utm_source=release-post&utm_id=v1-announcement&utm_content=integrations) makes it easy to connect with popular coding languages and web tools. When it comes to languages, Meilisearch supports them all, with special optimizations for any language that uses whitespace to separate words, plus Chinese, Japanese, Hebrew, Thai, and Korean.

> We found that, with our prior search engine (**Elasticsearch**), **14%** of searches resulted in a purchase, and with _**Meilisearch**, **20%**_ of searches were resulting in a purchase. That's a **huge improvement** without a lot of development time: 1 out of 5 customers found the book they were looking for and purchased it.  
> \- Andy Hunter, CEO of [Bookshop.org](https://Bookshop.org)

<Callout>
  Check [Bookshop.org full customer story](/blog/bookshop-increases-search-based-purchases/)
 </Callout>

From e-commerce to SaaS, media, and beyond, businesses from all industries trust Meilisearch to power their search needs. Don't let lackluster search hold you back any longer: [try Meilisearch today](https://www.meilisearch.com/?utm_source=release-post&utm_id=v1-announcement&utm_content=landing).

Why do companies love Meilisearch?
==================================

Simplicity
----------

We're a team of developers who understand the importance of a great developer experience. Even if you have the most flexible and powerful tool in the world, it doesn’t count for much if it’s painful to use and understand. That's why we made Meilisearch: to give developers the tool they need to create awesome search experiences, without provoking headaches or gray hairs.

The **consistency** and **predictability** of Meilisearch’s design make it easy to integrate into your chosen technical stack. Our comprehensive [documentation](https://docs.meilisearch.com/?utm_source=release-post&utm_id=v1-announcement&utm_content=docs) and [developer tools](https://docs.meilisearch.com/learn/what_is_meilisearch/sdks.html?utm_source=release-post&utm_id=v1-announcement&utm_content=integrations2) are designed to help you from start to success.

**Meilisearch works out of the box with no configuration needed**. But we understand that every project is different, so we've made customization easy. You can tailor it to your needs in just a few minutes, so you don't have to be a search expert to get the most out of Meilisearch.

Relevancy
---------

Relevancy, meaning the quality and accuracy of the search results, is a crucial aspect of any search engine. Irrelevant or poor-quality results can lead to a poor user experience, reducing sales, and causing users to lose trust in your brand. Conversely, users are more likely to return to, trust, and engage with brands that provide relevant search experiences.

> As a user, it felt like magic compared to other solutions I've tried. I'm not sure whether it's related to how typo tolerance works or if it's related to the default settings. Still, right after setting up Meilisearch with no particular tweak, I've got fantastically relevant results.  
> \- Anthony Catel, Co-founder of [minipouce](https://www.minipouce.fr/)

Meilisearch provides a **pre-configured set of ranking rules** that enable you to achieve **high relevancy right out of the box**, while also accepting customization to meet individual needs. These default settings were developed iteratively by working directly with our users, and are sure to satisfy almost all use cases.

Performance
-----------

In today's fast-paced digital world, search plays a crucial role in user experience. Being able to deliver relevant results quickly is key to the success of almost any product.

One [report from Deloitte](https://www2.deloitte.com/content/dam/Deloitte/ie/Documents/Consulting/Milliseconds_Make_Millions_report.pdf) shows that a mere 0.1s change in load time can have a noticeable influence on the user journey, increasing conversions by 8% for retail sites and 10% for travel sites.

**Meilisearch returns results in as little as 0.05s**. It is designed from the ground up for performance, making it an essential addition to your technical stack.

What’s included?
================

Search-as-you-type
------------------

For a long time, users were accustomed to typing search queries, pressing enter, and waiting for a page to load to view results. Those days are over, as technological improvements have ushered in the age of “search-as-you-type.”

By providing results instantly as the user types their query, **Meilisearch helps users make more precise searches and quickly find what they are looking for.** In today’s internet, “search-as-you-type” is a must-have feature that greatly improves overall satisfaction and retention.

Typo tolerance
--------------

Typos happen. [According to the VP of Search at Google](https://blog.google/products/search/abcs-spelling-google-search/), as many as 1 in 10 searches are misspelled. [A Baymard Institute UX study](https://baymard.com/research/ecommerce-search) also reports that out of 185 major e-commerce sites, 34% don’t return useful results when users misspell even a single character in a product title.

![](https://unable-actionable-car.media.strapiapp.com/where2watch_1_a98051676f.gif)

[See Meilisearch in action here](https://where2watch.meilisearch.com/?utm_source=release-post&utm_id=v1-announcement&utm_content=where2watch)

These statistics highlight the importance of using a search solution that can effectively handle spelling mistakes. **Meilisearch’s customizable typo tolerance allows for more accurate and relevant search results** even when users don’t type perfectly. Even better, it isn’t limited to Latin-based languages.

Faceted search
--------------

E-commerce merchants with large catalogs have a particular challenge to overcome. Potential buyers can get [overwhelmed by possibilities](https://neilpatel.com/blog/too-many-choices/), becoming less likely to make a purchase simply due to the effort of making a decision.

Fortunately, faceted search interfaces solve this problem.

Faceted search is a powerful tool that gives customers the power to apply filters and narrow down search results based on their needs and desires. By helping shoppers view the products they’re looking for based on criteria such as size, color, and style, the likelihood of a purchase is increased.

**Meilisearch makes it easy to integrate faceted search into any e-commerce storefront**. With just a few lines of code, you can upgrade your store's search capabilities, increasing sales and customer satisfaction.

Geo search
----------

Geo search, also known as location-based search or local search, is becoming increasingly important for modern web applications. With the fast-paced nature of today's world, people are constantly on the move and looking for quick and easy ways to find the information they need, such as **nearby businesses, services, or other points of interest**.

Meilisearch meets this need, providing simple methods to [sort search results by their location or filter results based on a geographic radius](https://docs.meilisearch.com/learn/advanced/geosearch.html?utm_source=release-post&utm_id=v1-announcement&utm_content=geosearch2). This helps developers build more personalized and modern applications.

API keys and multi-tenant indexes
---------------------------------

Thanks to [fine-grained API key management](https://docs.meilisearch.com/learn/security/master_api_keys.html?utm_source=release-post&utm_id=v1-announcement&utm_content=API-key-management), you can personalize **Meilisearch to comply with your organization’s security requirements**. Create API keys with custom permissions and expiration dates to ensure secure and flexible access to your data.

If your application is storing sensitive data from multiple users in the same index, it's very important that each user can only search for their own documents. You can trust Meilisearch’s many SDKs to provide methods to generate [tenant tokens](https://docs.meilisearch.com/learn/security/tenant_tokens.html?utm_source=release-post&utm_id=v1-announcement&utm_content=multitenancy2).

What’s next?
============

We will stay devoted to our core concepts of simplicity, speed, and relevance to keep empowering all builders.

We’ll keep collaborating with the open-source community and focusing on the Developer Experience to ensure **Meilisearch users can provide the best search experience in their websites and applications**.

Start building with Meilisearch v1.0
====================================

You can **get started with Meilisearch in just a few minutes**—everything works out of the box, no configuration required! All you need to do is choose the hosting solution that fits your business requirements, add documents, and you’re off.

### Try our solution: Meilisearch Cloud

Need to build fast, be compliant, or save resources? [Meilisearch Cloud](https://www.meilisearch.com/pricing?utm_source=release-post&utm_id=v1-announcement&utm_content=cloud) takes care of everything, so you can focus on the most important thing: making your users happy.

### Build your own solution: self-hosting

Since Meilisearch is open-source, you can host your own Meilisearch instance. Run Meilisearch and start searching through your data in less than five minutes by following our [quick start guide](https://docs.meilisearch.com/learn/getting_started/quick_start.html?utm_source=release-post&utm_id=v1-announcement&utm_content=quick-start).

🧰 For both solutions, we provide a large number of [developer tools](https://docs.meilisearch.com/learn/what_is_meilisearch/sdks.html?utm_source=release-post&utm_id=v1-announcement&utm_content=integrations3) and [reliable documentation](https://docs.meilisearch.com/?utm_source=release-post&utm_id=v1-announcement&utm_content=docs2) to help you connect your code base with Meilisearch.

Meilisearch 1.0: the next stage in search

We are thrilled to announce that the first major release of Meilisearch is here! It's the result of the combined efforts of many people. We are proud to release a completely stable version of Meilisearch, which will guarantee compatibility with future versions of Meilisearch. We are very grateful to our community, which has supported us and helped us to get this far.

Let's take a look at some of the most significant changes. You can read the [full changelog](https://github.com/meilisearch/meilisearch/releases/tag/v1.0.0) on GitHub, but we’ll go over the main ones in this article.

New feature: Korean support
---------------------------

Meilisearch is multilingual and features optimized support for several languages. Thanks to our amazing contributor [qbx2](https://github.com/qbx2), we now support Korean as well.

Improvement: language support
-----------------------------

Thanks to the engagement, feedback, suggestions, and PRs of our global community, we improved language support all around with notable enhancements for Chinese:

*   Transliteration of Chinese characters into [Pinyin](https://en.wikipedia.org/wiki/Pinyin) to improve relevancy
*   Updates to [our Chinese segmenter](https://crates.io/crates/jieba-rs) to remove [inconsistencies](https://github.com/meilisearch/charabia/issues/136) when splitting text into words
*   Unification of [Chinese character variants](https://www.unicode.org/reports/tr38/#N10211) to enhance Chinese normalization

We are always looking to improve, join the [discussion](https://github.com/meilisearch/product/discussions/503) about Chinese support on GitHub!

We have also implemented a new, more efficient [normalizer](https://github.com/meilisearch/charabia/blob/main/CONTRIBUTING.md#implement-a-normalizer) to remove [accents and other non-spacing marks](https://www.compart.com/en/unicode/category/Mn), which refines the support of Hebrew, Thai, Arabic, and Latin languages.

Improvement: one-step upgrade
-----------------------------

Users of Meilisearch v0.20 or below had to perform a two-step migration to be able to use their database with any version above 0.24. Until now.

v1.0 is compatible with dumps from all previous versions.

We have simplified the process so that anyone can smoothly migrate to our first major version! Check the [updating guide](https://www.meilisearch.com/docs/learn/update_and_migration/updating) in our documentation.

Improvement: indexing and search speed
--------------------------------------

*   We have reduced memory usage of search requests containing multiple long words.
*   We have also reduced the computational complexity of the exactness ranking rule and have implemented a caching system, resulting in a significant improvement in its performance, especially for search queries containing many words.
*   When interpreting a search query, multi-word synonyms are no longer treated as regular search query terms, but as phrases. Suppose you set San Francisco and SF as synonyms. The following search request:  
    `I am going to SF soon`  
    will now be interpreted as:  
    `I am going to "San Francisco" soon`  
    This change prevents requests containing multi-word synonyms from exceeding the word length limit and degrading the search performance. At the same time, it removes a source of denial-of-service attacks, and improves the relevancy of the search results.
*   We have tweaked the behavior of the proximity rule for search requests ending with prefixes or very short words to achieve substantial speed improvements.
*   Before v1.0, if the settings object contained searchable attributes, updating the settings always triggered a reindex. Now, Meilisearch checks if any changes were made to avoid unnecessary reindexing. Many thanks to [GregoryConrad](https://github.com/GregoryConrad) for implementing this!

Breaking changes
----------------

You will be happy to learn that the following are the last breaking changes we are going to introduce until v2.0 🥳 You can relax for a while, v2.0 is not yet planned ☺️

Check our [new versioning policy](https://github.com/meilisearch/engine-team/blob/main/resources/versioning-policy.md) to learn more about breaking changes.

### New master key security requirement

‌‌To strengthen security, Meilisearch now requires master keys to be at least 16 bytes when the [server environment](https://docs.meilisearch.com/learn/configuration/instance_options.html#environment) is set to `production`. If none is provided or if it doesn’t meet the criteria, Meilisearch will suggest a secure autogenerated master key you can use when restarting your instance.

### Primary key inference revamp

When creating an index or adding documents to Meilisearch, you can set the primary key explicitly or let Meilisearch infer it from your dataset.

To guess the primary key, also known as inference, Meilisearch used to look in your first document for an attribute **containing** the string `id`. Now, it looks for an attribute **ending** with the string `id`.

Furthermore, if multiple attributes ending with `id` are detected, Meilisearch will now throw an error asking you to specify the primary key manually using the [update index endpoint](https://docs.meilisearch.com/reference/api/indexes.html#update-an-index).

### New CLI behavior

`--max-index-size` and `--max-task-db` have been removed as they were not actually limiting the disk space taken by Meilisearch. This change has two consequences:

1.  Due to operating system limits on the amount of virtual memory allocatable by a single process, the number of indexes that can exist simultaneously in a Meilisearch database are:

*   around 200 for Linux/MacOS
*   around 20 for Windows

2\.  The size of an index is limited to 500GiB

While we plan on lifting the limitations described above in v1.1, if any of these changes affect you, it would be of great help to have [your input](https://github.com/meilisearch/product/discussions/567#discussioncomment-4634432). You can find more details in this [GitHub discussion](https://github.com/meilisearch/product/discussions/567).

Since its introduction in v0.26, the auto-batching feature has proven its worth. The `disable-auto-batching` CLI option and the associated environment variable `MEILI_DISABLE_AUTO_BATCHING`, which had been kept for debugging purposes, are no longer needed and have been removed.

‌‌We’re also removing the `--snapshot-interval-sec` flag to make scheduling snapshots simpler.

Before:‌‌

```bash
meilisearch --schedule-snapshot --snapshot-interval-sec 3600
```

After:

```bash
meilisearch --schedule-snapshot 3600
# If no value is provided, Meilisearch will take a new snapshot every 24 hours.
```

‌‌‌‌Finally, for the sake of consistency, the `--dumps-dir` CLI option has been renamed to `--dump-dir`, which is more idiomatic and in conformity with other existing options.

### Error handling improvements

To provide greater clarity and predictability in the use of the API, we have added granular error codes and a new `system` error type. You can consult the detailed list in the [changelog](https://github.com/meilisearch/meilisearch/releases/tag/v1.0.0).

Contributors
------------

A big thank you to all our contributors! We couldn't have reached this milestone without your support. You're really, truly great and we can't thank you enough for all the effort, suggestions, comments, and time you dedicate to Meilisearch. We are so grateful to have such an amazing community.

This month, we want to send a special shout-out to [@amab8901](https://github.com/amab8901), [@colbsmcdolbs](https://github.com/colbsmcdolbs), [@elbertronnie](https://github.com/elbertronnie), [@funilrys](https://github.com/funilrys), [@jiangbo212](https://github.com/jiangbo212), [@mohitsaxenaknoldus](https://github.com/mohitsaxenaknoldus), and [@shivaylamba](https://github.com/shivaylamba) for their help with [Meilisearch](https://github.com/meilisearch/meilisearch), and to [@amab8901](https://github.com/amab8901), [@GregoryConrad](https://github.com/GregoryConrad), and [@pnhatminh](https://github.com/pnhatminh) for their contributions to [Milli](https://github.com/meilisearch/milli). Likewise, we would like to thank [@choznerol](https://github.com/choznerol), [@crudiedo](https://github.com/crudiedo), [@daniel-shuy](https://github.com/daniel-shuy), [@harshalkhachane](https://github.com/harshalkhachane), [@mosuka](https://github.com/mosuka), [@qbx2](https://github.com/qbx2), [@Roms1383](https://github.com/Roms1383), [@Sokom141](https://github.com/Sokom141), and [@yenwel](https://github.com/yenwel) for their precious support on [Charabia](https://github.com/meilisearch/charabia).

Meilisearch latest news and company updates