Add support for docker compose (build, up, exec, ps, restart) · rtk-ai/rtk#1727

(2 comments) (0 reactions) (0 assignees)Rust (2.914 forks)batch import

area:clienhancementhelp wantedpriority:medium

Métricas do repositório

Stars: (48.085 stars)
Métricas de merge de PR: (Mesclagem média 11d 1h) (45 fundiu PRs em 30d)

Description

Problem

rtk discover flagged docker-compose as my single largest unhandled command surface — across 30 days I had:

docker compose ... — 724 invocations
docker-compose build — 222
docker-compose up — 194
docker-compose exec — 185
docker-compose ps — 101

Total: ~1,426 invocations not benefiting from RTK. docker exec is already handled (rtk docker), but the compose family isn't.

Proposal

A rtk compose <subcommand> (or auto-detection of docker compose ... / docker-compose ...) that compresses the same way rtk docker does:

build — collapse layer-cached steps, surface only actual build steps + warnings/errors
up / up -d — drop ASCII spinners and "Container ... Started" noise; one line per service
ps — same compact table style as rtk docker ps
exec — passthrough (no compression needed, but routes through hook)
restart — ok <service> style, like rtk git push

Why it matters

For projects on docker-compose, every up/build/ps cycle dumps hundreds of tokens of progress UI into Claude's context. Estimated savings on my usage alone: ~80% on build/up output.

Guia do colaborador

Direção de pesquisa: Estude a implementação existente do rtk docker para entender o padrão de compressão da saída de comandos e, em seguida, implemente manipuladores semelhantes para os subcomandos do docker compose: build, up, exec, ps, restart. Garanta o encaminhamento adequado para o exec.
Pilha de tecnologia: rust
Domain: backendclidevops
Tipo Issue: Funcionalidade
Difficulty: 2
Tempo estimado: Meio dia
Status da atividade: Ativo
Clarity: Claro
Prerequisites: RustGit
Simpatia para novatos: 70