cd /news/developer-tools/self-host-memos-with-docker-compose-… · home › topics › developer-tools › article
[ARTICLE · art-171754] src=dev.to ↗ pub= topic=developer-tools verified=true sentiment=· neutral

Self-Host Memos with Docker Compose: A Production Setup Guide

A developer published a production setup guide for self-hosting Memos, an open-source, timeline-based note-taking app, using Docker Compose. The guide covers a single-container deployment with an embedded SQLite store, a named volume at /var/opt/memos for the database and attachments, localhost-only port binding on 5230, and reverse-proxy configuration examples for Caddy and Nginx that forward Host and X-Forwarded-Proto headers. It advises registering the first account as admin before public exposure and notes that no separate database or cache container is needed for a standard deployment.

recommendation

For a single-instance Memos deployment, use a named volume at /var/opt/memos instead of a bind mount and bind port 5230 to 127.0.0.1 behind a TLS-terminating proxy.

more in playbook: Running AI in production
by read4 min views3 publishedNov 18, 2026

This tutorial was written with AI assistance from the project's official documentation. Verification status is stated at the end of the article.

Memos is a self-hosted note-taking app built around a personal timeline. Each memo is timestamped, Markdown-capable, and taggable, so short thoughts and longer entries live in one searchable stream. You control visibility per memo: private, shared with specific users, or public on the web. The app ships as a single Go binary with an embedded SQLite store by default, which makes it one of the lighter services to run on a VPS.

The upstream project does not publish a minimum RAM figure. Practical sizing depends on workload: an idle instance with a handful of users and a few thousand memos runs comfortably in a small container, while heavy attachment uploads, large media libraries, and many concurrent users push memory and disk usage up. Watch the volume size more than the RAM line.

Everything Memos keeps lives under /var/opt/memos inside the container. That directory holds the SQLite database, uploaded attachments, and generated thumbnails. Back it up as a unit.

docker compose version). 127.0.0.1:5230 first.5230 is the documented HTTP port. Bind it to localhost and let a reverse proxy terminate TLS.memos_data, mounted at /var/opt/memos. Do not use a bind mount to an arbitrary host path; a named volume keeps ownership and permissions consistent across image upgrades.neosmemo/memos. Tags: stable follows stable releases, a month tag like 26.10 pins to that month's stable release, and canary follows development builds. Use Memos does not need a separate database or cache container for a standard deployment. SQLite is embedded. If you later move to an external database, that is a configuration change, not a Compose dependency you need on day one.

Create a working directory and write the Compose file and environment file.

mkdir -p ~/memos && cd ~/memos
cat <<'EOF' > compose.yml
services:
  memos:
    image: neosmemo/memos:${MEMOS_TAG:-stable}
    container_name: memos
    restart: unless-stopped
    ports:
      - "127.0.0.1:${MEMOS_PORT:-5230}:5230"
    environment:
      TZ: ${TZ:-UTC}
    volumes:
      - memos_data:/var/opt/memos

volumes:
  memos_data:
EOF

Generate the environment file. Memos itself does not require a secret in the container environment for a single-instance SQLite deployment; the first account you create becomes the admin. Keep the file for timezone, port, and image tag so the stack is reproducible.

cat <<EOF > .env
TZ=UTC
MEMOS_PORT=5230
MEMOS_TAG=stable
EOF

Start the stack:

docker compose up -d
docker compose logs -f memos

You should see the server bind on 5230. Open http://127.0.0.1:5230 from the host, or tunnel it from your laptop:

ssh -L 5230:127.0.0.1:5230 user@your-server

Then visit http://localhost:5230 locally. The first account you register is the admin. Do that before you expose the instance publicly.

Memos is a normal HTTP app behind a proxy. The important details:

Host and X-Forwarded-Proto so generated links and the web UI use the correct scheme.Upgrade/ Connection headers will cause reconnect loops. Caddy example (/etc/caddy/Caddyfile):

memos.example.com {
    encode zstd gzip
    request_body {
        max_size 25MB
    }
    reverse_proxy 127.0.0.1:5230 {
        header_up X-Forwarded-Proto {scheme}
        header_up Host {host}
    }
}

Nginx example:

server {
    listen 443 ssl http2;
    server_name memos.example.com;

    client_max_body_size 25m;

    location / {
        proxy_pass http://127.0.0.1:5230;
        proxy_http_version 1.1;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }
}

First-run hardening checklist:

Update the image and restart:

cd ~/memos
docker compose pull
docker compose up -d
docker compose logs -f memos

Back up the data volume. Stop the container first so SQLite is not mid-write:

docker compose stop memos
docker run --rm \
  -v memos_memos_data:/data \
  -v "$PWD":/backup \
  alpine tar czf /backup/memos-$(date +%F).tar.gz -C /data .
docker compose start memos

The volume name is <project>_memos_data; if your directory is ~/memos, the project name is memos, so the volume is memos_memos_data. Confirm with docker volume ls.

Two pitfalls worth knowing from the docs:

store/migration/README.md explain why; skipping it can leave the database in a state the current image will not open.MEMOS_TAG to a month tag such as One more operational note: attachments live inside the same volume as the database. A backup that copies only the SQLite file will restore your memos without their images. Archive the whole /var/opt/memos tree, as the command above does.

Measured in our sandbox run: total memory 18.5 MB (sum of per-container peaks over a 30s idle window after startup) across 1 container; largest container 18.5 MB; published port(s) 5230; HTTP probe returned 200. The run took 41.5s including the image download.

Verification: we ran this docker-compose stack in a disposable Docker environment and recorded the measurements above. They describe that run, not a guarantee for your host.

Originally published with full interactive benchmark metrics and server sizing notes at https://benchrun.pages.dev/self-host-memos-docker-compose/.

── more in #developer-tools 4 stories · sorted by recency
simonwillison.net · · #developer-tools
llm 0.37.3
── more on @memos 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/self-host-memos-with…] indexed:0 read:4min 2026-11-18 · —