Docker Compose generator

Writing a Compose file by hand means juggling image names, port numbers, volume paths and which database goes with what. This generator does the juggling: pick your services, tune the essentials, and download a valid docker-compose.yml — with port conflicts caught, companion containers (databases, brokers) wired in automatically, and downloads routable through a VPN kill switch.

Start from a preset:

Your stack

docker-compose.yml

Starting point, not a finished product. A generated Compose file is a starting point, not an audited production configuration. Before you deploy: review every image and its tag — tags like :latest, :stable and :release float, so pin an exact version for any service you can't afford to have change under you — check the published ports and volume paths against your own machine, and replace every placeholder password. Each service's linked guide explains what you're actually running.

Save it on your NAS, review the paths and secrets once, then docker compose up -d. New to Compose? The Compose basics guide explains what every section does.

How it works

Every service in the catalog carries the same definition used in this site's guides — image, ports, volumes, environment — so the file you download is the file the guides describe. Three kinds of quiet help happen while you build: companions (Immich and Paperless bring their database and cache containers with them, wired with matching passwords), conflict detection (two services claiming the same host port — Zigbee2MQTT and qBittorrent both love 8080 — get flagged before your NAS finds out the hard way), and suggestions (an *arr app with no indexer or download client is a car with no engine; the generator notices and offers the missing piece in one click).

Frequently asked questions

Is the generated file really valid Compose?

Yes — the generator builds your stack from the same service definitions used in this site's guides, and every preset and combination is machine-checked against a YAML parser. You still choose your own folder paths and secrets; the generator flags placeholder passwords so you do not deploy them by accident.

Where do the folder paths come from?

Two global settings: a config root (where each service's settings live, one folder per service) and a media root (your libraries). They default to typical NAS layouts (/volume1/docker and /volume1/media) — change them to match your machine, e.g. /mnt/user/appdata on Unraid or a folder on your Linux box, and every volume line updates.

What does 'route through Gluetun' actually change?

It removes the download client's own port mappings, gives it network_mode: service:gluetun so all its traffic rides the VPN tunnel, and publishes its ports on the Gluetun container instead — the standard kill-switch pattern from our Gluetun guide. If the VPN drops, the client simply has no network, which is the point.

Can I edit the result afterwards?

Please do — it is a normal docker-compose.yml, meant to live on your NAS and evolve. The generator is a starting line with the boring parts (depends_on, database containers, environment wiring) already correct, not a lock-in.

Related guides