Mealie: Self-Hosting a Recipe Manager & Meal Planner on Your NAS

If you are tired of losing recipes to broken links, scattered browser bookmarks, and a folder full of screenshots that you can never search, Mealie is the self-hosted recipe manager and meal planner that finally puts your digital cookbook in one searchable place. This guide walks you through setting up Mealie on your NAS using Docker, covers the most common setup mistakes, and explains when you need to upgrade the database for a multi-user household. By the end, you will have a family-friendly meal planner that generates shopping lists from your weekly menu — no subscription required. This guide breaks down mealie recipe manager in practical terms.

What Does Mealie Do? URL Import, Meal Planning, and Shopping Lists

Mealie is a self-hosted web application that does three core things for a homelab household. First, it imports recipes from a URL — paste a link from Allrecipes, Serious Eats, BBC Good Food, or dozens of other sites, and Mealie extracts the ingredients, instructions, cook time, and nutrition data automatically. Second, it provides a meal planning calendar where you drag recipes onto specific days, set serving sizes, and see what you are cooking for the week. Third, it generates a shopping list from the planned meals, consolidating duplicate ingredients across recipes.

Unlike cloud-based recipe apps, Mealie stores everything on your own NAS. No data leaves your network, no subscription fees, and no risk of a service shutting down and taking your recipe collection with it. The search is fast — you can filter by tags, categories, ingredients, or full-text across your entire library.

Mealie Setup Guide: Docker Compose on Your NAS

The cleanest way to deploy Mealie on a NAS is with Docker Compose. This works on TrueNAS SCALE, Unraid, Proxmox (via a Docker LXC), or any Linux server running Docker. The container is lightweight and runs fine alongside other services like Jellyfin or a file server. For a dedicated Docker host build, check out our Best Docker Server Build 2026 guide.

Basic Docker Compose File for Mealie

Create a directory on your NAS for Mealie data, then save the following as docker-compose.yml:

version: "3.7"
services:
  mealie:
    image: ghcr.io/mealie-recipes/mealie:latest
    container_name: mealie
    restart: always
    ports:
      - "9925:9000"
    volumes:
      - ./mealie-data:/app/data
    environment:
      - BASE_URL=https://mealie.yourdomain.com
      - DB_ENGINE=sqlite
      - TZ=America/New_York

Run docker compose up -d in that directory. Mealie will initialize the SQLite database automatically on first launch. Access the web UI at http://your-nas-ip:9925.

Persistent Volume for the Database

The ./mealie-data:/app/data volume mount is critical. This is where Mealie stores its SQLite database, recipe images, and user settings. Without it, every container restart would wipe your data. Point this volume to a dataset on your NAS pool — ideally on a mirrored or RAID-Z array that is backed up separately. Remember, RAID protects against drive failure, not accidental deletion or ransomware. A separate backup strategy is still required.

SQLite vs PostgreSQL: When to Upgrade for a Family

Mealie supports two database backends: SQLite (default) and PostgreSQL. For a single user or a couple who imports a few dozen recipes and plans one week of meals at a time, SQLite is perfectly adequate. It requires zero configuration, uses minimal RAM, and handles concurrent read operations well.

If you have a household of four where multiple family members are logging in, importing recipes, and editing the meal plan simultaneously, switch to PostgreSQL. SQLite uses file-level locking, which can cause “database is locked” errors under concurrent write load. PostgreSQL handles multiple writers gracefully and adds no noticeable overhead on a typical NAS.

Switching from SQLite to PostgreSQL

To migrate, add a PostgreSQL container to your Compose file, change the environment variables, and run the Mealie database migration. Here is the key change:

environment:
  - BASE_URL=https://mealie.yourdomain.com
  - DB_ENGINE=postgres
  - POSTGRES_USER=mealie
  - POSTGRES_PASSWORD=aStrongPassword
  - POSTGRES_SERVER=postgres
  - POSTGRES_PORT=5432
  - POSTGRES_DB=mealie

Add a postgres service alongside your Mealie service, with its own persistent volume. Mealie will automatically migrate the data on first launch with the new engine. Back up your SQLite database file before attempting this migration.

The Most Common Setup Mistake: Setting the BASE_URL Correctly

This single environment variable causes more headaches than any other Mealie configuration issue. If BASE_URL is wrong, the web UI loads but links, images, and the meal planner all break silently. The application uses this URL to generate absolute links for emails, OpenGraph previews, and internal API calls.

Common failure pattern: You set up a reverse proxy on port 443 but forget to update BASE_URL from the default (http://localhost:9000). The result is a working login page but broken recipe images and a non-functional meal planner. Always verify BASE_URL matches your access path after any proxy or port change.

Exposing Mealie Safely to Family Members Outside the LAN

Mealie is designed to be shared with family — but you should not expose it directly to the internet without protection. The safest approach is to run Mealie behind a reverse proxy with HTTPS and authentication. This allows family members who do not live in your house to access the recipe collection and meal plan without you opening ports to the Mealie container itself.

Setting Up a Reverse Proxy for Mealie

If you are running Unraid, the built-in Nginx Proxy Manager is a popular choice. For TrueNAS SCALE users, the Traefik app works well. Both integrate cleanly with Let’s Encrypt for free SSL certificates. If you are comparing NAS operating systems, our TrueNAS vs Unraid guide covers which platform handles reverse proxies more smoothly.

Mealie vs Tandoor: Which Self-Hosted Recipe Manager Fits Your Family?

Tandoor Recipes is the main alternative to Mealie in the self-hosted space. Both are open source, both run in Docker, and both support URL imports. But they differ in philosophy and target audience.

For a family setting where non-technical members will be the primary users, Mealie is the better choice. The URL import is more reliable, the meal planner is more polished, and the SQLite option means you can run it on a low-power NAS without setting up a separate database server. Tandoor is a capable alternative if you prefer a more traditional database backend and do not mind occasional manual recipe cleanup.

Bottom Line: Should You Self-Host Mealie on Your NAS?

If you have ever lost a recipe to a broken link or spent ten minutes searching for a screenshot of a dish you cooked last month, Mealie is worth the 15-minute setup time. It runs on any NAS that supports Docker, uses negligible system resources, and gives every family member a shared, searchable cookbook that works on phones, tablets, and laptops.

Start with SQLite and the basic Docker Compose file. Once you have a few dozen recipes imported, introduce the meal planner. If the household grows to three or more active users, plan a weekend migration to PostgreSQL. Expose it behind a reverse proxy with HTTPS so relatives can browse your recipe collection from their own homes. And remember — back up the Mealie data directory alongside the rest of your NAS data, because no amount of RAID replaces a real backup.