Self-host Meilisearch with Levelrail
VerifiedA fast, typo-tolerant search engine API you can drop into any app's search bar.
- Authormeilisearch
- LicenceMIT
- Memory512 MiB
- Archarm64
- Services1
How to self-host Meilisearch
-
Pull the images
One image is pulled on your server.
Show images
getmeili/meilisearch:v1.11.1
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 7700.
-
Fill in the secrets
1 secret is generated and stored encrypted, 1 setting is preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Meilisearch requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 7700
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- MIT, permissive license
- Verified. Verified on arm64 with image tag v1.11.1. Our CI ran this exact image version and it answered on its health path. Evidence
- Host ports. It publishes port 7700 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Meilisearch. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Meilisearch docs page.
Deploy Meilisearch your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Meilisearch from the CLI
levelrail-cli templates deploy meilisearch --name my-meilisearch Deploy Meilisearch with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/meilisearch/deploy Meilisearch configuration
Meilisearch services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| meilisearch | getmeili/meilisearch:v1.11.1 | 7700 | meilisearch_data -> /meili_data |
Meilisearch environment variables
| Variable | Service | Value |
|---|---|---|
| MEILI_MASTER_KEY | meilisearch | Generated at deploy |
| MEILI_NO_ANALYTICS | meilisearch | Preset by the template |
Ports and volumes
- Ports
- 7700
- Volumes
- 1 named mount: meilisearch_data -> /meili_data
Meilisearch FAQ
How much memory does Meilisearch need?
The catalog lists about 512 MiB of memory for Meilisearch.
Does Meilisearch run on arm64?
For Meilisearch, arm64 is tested; amd64 is image published.
What licence is Meilisearch under?
Meilisearch is licensed under MIT, which is permissive, with few conditions on reuse.
Does Meilisearch need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which ports does Meilisearch use?
Meilisearch listens on port 7700 inside the stack.
Where does Meilisearch keep its data?
In a named volume: meilisearch_data mounted at /meili_data.
Can I deploy Meilisearch on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id meilisearch for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image getmeili/meilisearch:v1.11.1 is what you deploy there.