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. 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 <