Features06 Compose

Projects, not piles of containers.

Every compose project as one group, with up and down, and as a diagram you can take to draw.io. See which service lags behind its compose file, update a project in one move, and rebuild just the service you touched. And take a project to your own server: see what goes along, copy or move it, and update it there from here.

One file, a whole project?Read the comic: one recipe card for the whole dinner, and a dinner that moves to Cas’s kitchen at home →
Fig. — The compose page, with the menu of a service built from a Dockerfile: rebuild or recreate.

What you can do

Projects as a group

Up and down for the whole project. After down it stays on the list.

The compose file

Edit a project's compose file straight from the app, in the editor of VS Code, and read the configuration compose makes of it. Compose reads it before it is saved. The .env beside it, and the files its services name under env_file, open in the same dialog; after saving one, a button redeploys the project.

Open in your editor

The menu of a project opens its folder in the editor you have: VS Code, Cursor, VSCodium, Windsurf or VS Code Insiders, one line each. Without any of them, or with the folder in a WSL distro, the menu or the message says so.

Earlier versions

Each time the editor overwrites the file, what was there is kept: the last 30, or anything from 5 to 200. See the difference with what you have now, line by line, put an old version back in the editor, or give it a note, and a version with a note stays. A .env is never kept.

From docker run to compose

Paste one or more docker run commands and get a compose.yaml. Nothing is run. A flag compose does not know is listed under the file instead of dropped, and compose reads the result before you copy or save it.

Containers as a compose file

Write the containers that run now as one file, with their networks and volumes marked external so it hangs on the data that is already there. Passwords are hidden on screen and present in what you save; a container that is already in a project is skipped.

The project as a diagram

Networks, services with their ports, volumes and folders on one sheet, with depends_on between the services. Drag blocks and lines, and save it as a .drawio file or open it in draw.io.

Drift

See which service still runs on settings from before you edited the compose file.

Resilience

What happens when a service stops, stalls or loses its data: no healthcheck, depends_on that does not wait until healthy, no restart policy, a database without a backup. Where it can, the app writes the change as a diff.

Back up the project

All its volumes, paused together, with the compose files and the .env, in one folder. Restore it as a whole: the project stops meanwhile and starts again in the order of depends_on.

Update a project

Pull and recreate in one go, renewing only the services that changed.

Rebuild or recreate one service

Each service has its own menu. Recreate makes a new container from the same image with the compose file as it is now; for a service with build:, rebuild makes a new image first, with the build output in view. A rebuild can be cancelled from the task list, and a failed one comes with a diagnosis.

Profiles

Services in a profile that are not started are named on the project, and Profiles… chooses which ones join when you start it; the app remembers that per machine, because compose does not. Stopping always takes every profile down, so nothing is left running and the network goes too. A template or a git project lets you choose them when you deploy.

Passwords from your password manager

Put pass://vault/item/field (Proton Pass) or op://… (1Password) in the .env instead of a password. When the project starts, the app runs compose through the command line of the manager: the values go only into that command, never on disk, and the app never sees them. Without a reference nothing changes, and nothing extra is needed.

Init steps and jobs

An init step (pre_start) sits with its service and does not count as a second container; a failed one shows its exit code, links to its logs and can be cleared. Jobs from the compose file, which Compose never starts by itself, get a button to run them, with their output.

Watch

Start docker compose watch for a project from its menu, or pick the services to follow and, if you like, their logs alongside through up --watch. It builds, starts and follows the files the compose file names, and the output stays in the project's card until you stop it.

From the catalog

Pick a ready-made project from a template list, fill in its fields and deploy it after a review, or keep one of yours as a template. More on the Catalog page.

From git

Clone a repository over https or ssh, see what its compose file asks of your engine (privileged, the Docker socket, system folders, builds), and deploy it only after that. Everything its compose files read, through include, extends or env_file, must stay inside the repository, also through a link. Later, update shows the new commits, moves forward only by fast-forward (a tag follows where it moved), and reviews the file again: what a new commit adds to what it asks of your engine, and what it no longer needs. If it does not deploy, Back returns to the commit that ran. A private repository works with a token or an SSH key of its own, stored encrypted and only sent to that address. Like a template from the catalog, it runs in a clean environment.

To another machine

A wizard that shows what goes along before anything moves: images, volumes with their size, the folders and files it mounts from this computer, another architecture.

Folders and files, decided

Per folder or file a choice: a volume filled with what is here, a config with its content, a folder on the server, or left out. Moving to WSL on this computer, a folder under C:\ can also stay where it is, through /mnt/c. A big folder is measured first and proposed to be left out. Your own compose file stays as it is.

Ports, decided

A port taken there is found first, even by a program outside Docker. Keep the same port, pick another one there, or leave it unpublished; another port is checked right away.

Copy or move, and back

Step by step, with how far a long step is and the time it took. If a step fails, the app removes what it put there and starts the project here again.

Update it there from here

Edit the compose file or a folder here, see what that changes there, and put it there again. Data volumes stay as they are.

The compose file

Edit it where you see it.

The file of a project opens in Monaco, the editor of VS Code, in the colours of the app, and Ctrl+S saves it. Before anything is written, compose reads the new text, so a typo does not reach your next up: you see what compose says, with the line. If the file changed outside the app in the meantime, you choose between reloading and overwriting. The app writes only the compose files of that project, and a dialog with unsaved changes does not close on Escape.

Fig. — The compose file of shop in the editor: a restart policy added, not saved yet.

Overview

The whole project on one sheet.

Overview… in the menu of a project draws it the way you would in draw.io: networks on the left, the services with their ports in the middle, volumes and folders on the right. It reads compose config, so a service that never started is there too, dashed; a running one is green, a stopped one red. Lines keep square corners and jump where they cross. Drag a block and the lines follow; drag a line to route it yourself. Save it as a .drawio file, or open it in draw.io as it is on screen. The same overview opens from the group of the project on Containers.

Fig. — The overview of infra: two networks, seven services with their ports, and the volumes and folders they use.

Resilience

What breaks when a service does, and the line that prevents it.

Resilience… in the menu of a project reads compose config and the containers: a service without a healthcheck, one that starts before its database is ready, one that stays down after a crash, a database whose volume has no backup schedule. For the fixed cases the app writes the change itself (restart: unless-stopped, a healthcheck for images it knows such as Postgres and Redis, condition: service_healthy) and shows it as a diff. Apply saves it through the editor, after compose has read it. Explain and propose lets the AI write the rest, one key of one service, checked by compose before and after.

Fig. — The resilience of shop: a database without a backup, no restart policy, and the healthcheck the app writes for Postgres, as a diff.

Your own server

The folders your project mounts do not exist there.

A bind mount like ./data is a path on this computer. On a server, Docker quietly makes an empty folder of it, and the project starts without its data. The app sees that first, and turns such a folder into a volume filled with what is here, or a single file into a config with its content.

Good to know

Compose needs the docker CLI. Nothing else does.

Up and down run through the docker CLI with the compose plugin, exactly as in your terminal. Everything else in the app talks to the Engine API directly.

All features

Try it on your own daemon.
Free and open source. Windows installer, Linux AppImage, or npx on any platform.
Download for Windows
$ npx docker-client-mx