Self-host Mealie with Levelrail
VerifiedA self-hosted recipe manager and meal planner with a clean web UI and API.
- Authormealie-recipes
- LicenceAGPL-3.0-only
- Memory512 MiB
- Archarm64
- Services1
How to self-host Mealie
-
Pull the images
One image is pulled on your server.
Show images
ghcr.io/mealie-recipes/mealie:v3.28.0
-
Create the app
One service starts in a single Compose app, with 1 named volume mount for your data, on port 9000.
-
Fill in the secrets
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.
Mealie requirements
- Memory
- About 512 MiB
- Architectures
- amd64 image published, arm64 tested
- Ports
- 9000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- AGPL-3.0-only, network copyleft (agpl) license
- Verified. Verified on arm64 with image tag v3.28.0. Our CI ran this exact image version and it answered on its health path. Evidence
- Host ports. It publishes port 9000 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 Mealie. 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 Mealie docs page.
Deploy Mealie your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Mealie from the CLI
levelrail-cli templates deploy mealie --name my-mealie Deploy Mealie with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/mealie/deploy Mealie configuration
Mealie services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| mealie | ghcr.io/mealie-recipes/mealie:v3.28.0 | 9000 | mealie_data -> /app/data |
Mealie environment variables
| Variable | Service | Value |
|---|---|---|
| BASE_URL | mealie | Preset by the template |
Ports and volumes
- Ports
- 9000
- Volumes
- 1 named mount: mealie_data -> /app/data
Mealie FAQ
How much memory does Mealie need?
The catalog lists about 512 MiB of memory for Mealie.
Does Mealie run on arm64?
For Mealie, arm64 is tested; amd64 is image published.
What licence is Mealie under?
Mealie is licensed under AGPL-3.0-only, which is network copyleft, so source sharing also applies when it is offered as a hosted service.
Does Mealie need configuration before it starts?
No. The template fills in its own defaults.
Which ports does Mealie use?
Mealie listens on port 9000 inside the stack.
Where does Mealie keep its data?
In a named volume: mealie_data mounted at /app/data.
Can I deploy Mealie 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 mealie for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image ghcr.io/mealie-recipes/mealie:v3.28.0 is what you deploy there.