Back to browse
GitHub Repository

A CLI tool to orchestrate multi-repository Docker environments

4 starsGo

Mdc – Orchestrate multi-repo Docker environments with one command

by tominaga-h·Feb 28, 2026·1 point·0 comments

AI Analysis

●●SolidSolve My ProblemShip It

Daemonizes foreground tasks (npm run dev) across repos, but solves a localized workflow problem.

Strengths
  • Genuinely useful for microservice teams: daemonizes npm/node tasks that docker-compose can't, with process tracking and log attach
  • Clean UX: color-coded output, process state table, explicit parallel/sequential modes in YAML
  • Zero friction adoption: single YAML config file, binaries pre-built, works with existing docker-compose setups
Weaknesses
  • Solves a niche pain specific to small teams with fragmented mono-repos; larger shops use orchestration (Kubernetes, Docker Swarm)
  • No evidence of adoption beyond the author's agency; feature set is straightforward wrapper logic
Target Audience

Microservice developers, agency engineers managing multi-repo codebases

Similar To

Docker Compose · Lerna · Turbo

Post Description

Hi HN!

I work at a software agency where I constantly have to deal with microservices and projects split across multiple repositories (e.g., Frontend, Backend API, Auth Service). Every morning, I found myself doing the same chore: opening multiple terminal tabs, navigating to different directories, and running `docker-compose up -d` or `npm run dev` one by one.

It was tedious, so I built *mdc (Multi-Docker-Compose)* to solve this exact problem.

*What it does:* `mdc` lets you define all your cross-repository commands in a single YAML file and orchestrates them with a single command: `mdc up`.

*Key features:* * *Parallel & Sequential Execution:* Boot up your entire stack concurrently, or sequentially if you have strict dependencies. * *Background Process Management:* It doesn't just run `docker-compose`. You can daemonize long-running foreground tasks like `npm run dev` (using `background: true` in the YAML) and easily monitor them with `mdc procs`. * *Clean UI:* Color-coded outputs and emojis to instantly see which project is failing or starting. * *Zero Dependencies:* Written in Go, distributed as a single binary. (This was actually my very first Go project!)

You can check it out here: https://github.com/tominaga-h/multi-docker-commander

I'd love to hear your feedback, thoughts on the architecture, or if you've faced similar local-dev nightmares. Happy to answer any questions!

Similar Projects

AI/MLMid

Multi-agent orchestration layer for experimentation

File-system driven agent config is clean, but OpenClaw and LangGraph already solve this.

Ship It
theo-kirby
1028d ago
Developer Tools●●Solid

49Agents – 2D Canvas IDE for Orchestrating Agents, Repos, Issues

Infinite canvas for agents beats terminal tab hell, but Steve Yegge's Beads tables are the real draw.

Big BrainBold Bet
alpadurza
2121mo ago
SecurityMid

I sandboxed OpenAI's Symphony orchestrator in one file using YSA

Example repo for YSA sandboxing when the main YSA product would be the actual submission.

Ship ItNiche Gem
jordanedev
202mo ago