Meilisearch

Search without ZooKeeper beside it. One container where Solr is two. A stack runs one search engine, so naming the other replaces it, and what is lost is an index that reindexes.

Your application finds it at MEILISEARCH_HOST, port 7700, and authenticates with MEILI_MASTER_KEY. Both are in its environment. The key is made for each environment and never changes, so the API keys Meilisearch issues under it stay valid across deploys.

It runs in production mode, so every request needs a key and the search preview page is off. Its index is kept on disk and survives a restart.

#Versions

Pin the version, not the build: name v1.53.1 and the platform matches it to the current build, so a security rebuild reaches you without anybody editing a repository.

The version you name is the one your environment runs from the next deploy. This service keeps data, and not every version can read another's — before you change it, read Changing a service's version.

#What you can change

In vallic.yaml — what each one does is on Service settings:

services:
  - meilisearch:
      version: 'v1.53.1'
      environment:
        MEILI_MAX_INDEXING_MEMORY: …
        MEILI_LOG_LEVEL: …

Anything not on this list refuses the deploy, naming the variable — rather than being accepted and quietly ignored.