<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: HiroItozzz</title>
    <description>The latest articles on DEV Community by HiroItozzz (@hiroitozzz).</description>
    <link>https://dev.to/hiroitozzz</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3724972%2F89436300-9ff6-4a01-9362-b78090231b04.png</url>
      <title>DEV Community: HiroItozzz</title>
      <link>https://dev.to/hiroitozzz</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/hiroitozzz"/>
    <language>en</language>
    <item>
      <title>Stop Typing Long Docker Compose Commands — compose-lazy Does It Interactively</title>
      <dc:creator>HiroItozzz</dc:creator>
      <pubDate>Wed, 03 Jun 2026 05:25:22 +0000</pubDate>
      <link>https://dev.to/hiroitozzz/compose-lazy-v080-interactive-docker-compose-cli-with-workspace-management-24nn</link>
      <guid>https://dev.to/hiroitozzz/compose-lazy-v080-interactive-docker-compose-cli-with-workspace-management-24nn</guid>
      <description>&lt;p&gt;If you work with Docker Compose daily, you've typed some version of this hundreds of times:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;docker compose &lt;span class="nt"&gt;-f&lt;/span&gt; docker-compose.prod.yml &lt;span class="nt"&gt;--profile&lt;/span&gt; dev &lt;span class="nb"&gt;exec &lt;/span&gt;app bash
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;compose-lazy&lt;/strong&gt; is a CLI tool I built to cut that down. It provides shorthand commands for the most common &lt;code&gt;docker compose&lt;/code&gt; workflows, and — more usefully — lets you pick compose files, profiles, and services interactively instead of remembering or typing them.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pipx &lt;span class="nb"&gt;install &lt;/span&gt;compose-lazy
&lt;span class="c"&gt;# or&lt;/span&gt;
uv tool &lt;span class="nb"&gt;install &lt;/span&gt;compose-lazy
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Three commands are added to your PATH: &lt;code&gt;dcp&lt;/code&gt;, &lt;code&gt;dcpu&lt;/code&gt;, and &lt;code&gt;dcpe&lt;/code&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  The basics: shorter commands
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# docker compose up --build -d&lt;/span&gt;
dcpu &lt;span class="nt"&gt;-b&lt;/span&gt; &lt;span class="nt"&gt;-d&lt;/span&gt;

&lt;span class="c"&gt;# docker compose exec app bash&lt;/span&gt;
dcpe app

&lt;span class="c"&gt;# docker compose logs app -f&lt;/span&gt;
dcp l app &lt;span class="nt"&gt;-fo&lt;/span&gt;

&lt;span class="c"&gt;# docker compose stop&lt;/span&gt;
dcp s
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The aliases map closely to the originals — &lt;code&gt;dcpu&lt;/code&gt; is always &lt;code&gt;docker compose up&lt;/code&gt;, &lt;code&gt;dcpe&lt;/code&gt; is always &lt;code&gt;docker compose exec&lt;/code&gt;, and &lt;code&gt;dcp&lt;/code&gt; is a general-purpose entry point for everything else (&lt;code&gt;build&lt;/code&gt;, &lt;code&gt;restart&lt;/code&gt;, &lt;code&gt;ps&lt;/code&gt;, &lt;code&gt;logs&lt;/code&gt;, &lt;code&gt;stop&lt;/code&gt;, &lt;code&gt;down&lt;/code&gt;, ...).&lt;/p&gt;




&lt;h2&gt;
  
  
  The useful part: interactive selection
&lt;/h2&gt;

&lt;p&gt;This is where compose-lazy earns its name. Pass an option flag without a value and it reads your project and prompts you to choose.&lt;/p&gt;

&lt;h3&gt;
  
  
  Pick a compose file with &lt;code&gt;-f&lt;/code&gt;
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;$ &lt;/span&gt;dcpu &lt;span class="nt"&gt;-f&lt;/span&gt;
☑ Found 2 compose files!
    1. docker-compose.yml
    2. docker-compose.prod.yml
Enter your choices &lt;span class="o"&gt;(&lt;/span&gt;e.g., 1,3,4&lt;span class="o"&gt;)&lt;/span&gt; or &lt;span class="s1"&gt;'q'&lt;/span&gt; to quit: 2
▷ Executing &lt;span class="sb"&gt;`&lt;/span&gt;docker compose &lt;span class="nt"&gt;-f&lt;/span&gt; docker-compose.prod.yml up&lt;span class="sb"&gt;`&lt;/span&gt;&lt;span class="nb"&gt;.&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Multiple selections work too — enter &lt;code&gt;1,2&lt;/code&gt; to use both files.&lt;/p&gt;

&lt;h3&gt;
  
  
  Pick a profile with &lt;code&gt;-pf&lt;/code&gt;
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;$ &lt;/span&gt;dcp re &lt;span class="nt"&gt;-pf&lt;/span&gt;
☑ Found 2 profiles!
    1. dev
    2. prod
Enter your choices &lt;span class="o"&gt;(&lt;/span&gt;e.g., 1,3,4&lt;span class="o"&gt;)&lt;/span&gt; or &lt;span class="s1"&gt;'q'&lt;/span&gt; to quit: 1
▷ Executing &lt;span class="sb"&gt;`&lt;/span&gt;docker compose &lt;span class="nt"&gt;--profile&lt;/span&gt; dev restart&lt;span class="sb"&gt;`&lt;/span&gt;&lt;span class="nb"&gt;.&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Pick a service with &lt;code&gt;-s&lt;/code&gt;
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;$ &lt;/span&gt;dcp l &lt;span class="nt"&gt;-s&lt;/span&gt;
☑ Found 3 services!
    1. app
    2. db
    3. frontend
Enter your choices &lt;span class="o"&gt;(&lt;/span&gt;e.g., 1,3,4&lt;span class="o"&gt;)&lt;/span&gt; or &lt;span class="s1"&gt;'q'&lt;/span&gt; to quit: 1,2
▷ Executing &lt;span class="sb"&gt;`&lt;/span&gt;docker compose logs app db&lt;span class="sb"&gt;`&lt;/span&gt;&lt;span class="nb"&gt;.&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For &lt;code&gt;exec&lt;/code&gt; and &lt;code&gt;run&lt;/code&gt;, the service prompt appears automatically when no service is given — no &lt;code&gt;-s&lt;/code&gt; needed:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;$ &lt;/span&gt;dcpe
☑ Found 3 services!
    1. app
    2. db
    3. frontend
Enter your choice or &lt;span class="s1"&gt;'q'&lt;/span&gt; to quit: 1
▷ Executing &lt;span class="sb"&gt;`&lt;/span&gt;docker compose &lt;span class="nb"&gt;exec &lt;/span&gt;app bash&lt;span class="sb"&gt;`&lt;/span&gt;&lt;span class="nb"&gt;.&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;There's also a small quality-of-life detail: &lt;code&gt;dcpe uv run pytest&lt;/code&gt; auto-detects that &lt;code&gt;uv&lt;/code&gt; isn't a service name, falls back to interactive service selection, and carries &lt;code&gt;uv run pytest&lt;/code&gt; forward as the inner command.&lt;/p&gt;




&lt;h2&gt;
  
  
  Workspace management: operate multiple repos at once
&lt;/h2&gt;

&lt;p&gt;The workspace feature is for projects that span multiple repositories. Register repos into a named workspace and run commands across all of them with a single prompt.&lt;/p&gt;

&lt;h3&gt;
  
  
  Register a repo
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;$ &lt;/span&gt;dcp ws register
Please enter a new directory path: /path/to/repo
☑ Found 2 docker-compose files!
    1. docker-compose.yml
    2. docker-compose.prod.yml
Enter your choices &lt;span class="o"&gt;(&lt;/span&gt;e.g., 1,3,4&lt;span class="o"&gt;)&lt;/span&gt; or &lt;span class="s1"&gt;'q'&lt;/span&gt; to quit: 1

☑ Found 1 registered workspace!
    1. myproject
Or &lt;span class="s1"&gt;'0'&lt;/span&gt; &lt;span class="k"&gt;for &lt;/span&gt;a new entry.
Enter your choice or &lt;span class="s1"&gt;'q'&lt;/span&gt; to quit: 0
Please enter a new workspace name: myproject

☑ Registered new path to myproject: /path/to/repo &lt;span class="o"&gt;(&lt;/span&gt;docker-compose.yml&lt;span class="o"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;You can register multiple repos into the same workspace. Each repo gets its own compose file pinned at registration time.&lt;/p&gt;

&lt;h3&gt;
  
  
  Bring up everything
&lt;/h3&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;$ &lt;/span&gt;dcp ws up
☑ Found 1 registered workspace!
    1. myproject
Enter your choice or &lt;span class="s1"&gt;'q'&lt;/span&gt; to quit: 1

───── 📂 myproject ──────────────────────────────────────────────────────────
▷ Executing &lt;span class="sb"&gt;`&lt;/span&gt;docker compose &lt;span class="nt"&gt;-f&lt;/span&gt; docker-compose.yml up &lt;span class="nt"&gt;-d&lt;/span&gt;&lt;span class="sb"&gt;`&lt;/span&gt; &lt;span class="k"&gt;in &lt;/span&gt;MYPROJECT.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;All workspace subcommands:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Command&lt;/th&gt;
&lt;th&gt;What it runs&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;dcp ws register(reg)&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Register a repo interactively&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;dcp ws delete(del)&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Remove a repo&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;dcp ws list(li)&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;Show all workspaces and their repos&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;dcp ws up(u)&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;docker compose up -d&lt;/code&gt; across all repos&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;dcp ws build(b)&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;docker compose build&lt;/code&gt; across all repos&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;dcp ws restart(re)&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;docker compose restart&lt;/code&gt; across all repos&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;dcp ws stop(s)&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;docker compose stop&lt;/code&gt; across all repos&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;dcp ws down&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;
&lt;code&gt;docker compose down&lt;/code&gt; across all repos&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Config lives in &lt;code&gt;~/.config/compose-lazy/config.yml&lt;/code&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  Requirements
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Python 3.11+&lt;/li&gt;
&lt;li&gt;Docker with Compose V2 (&lt;code&gt;docker compose&lt;/code&gt;, not &lt;code&gt;docker-compose&lt;/code&gt;)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;🔗 &lt;a href="https://pypi.org/project/compose-lazy/" rel="noopener noreferrer"&gt;PyPI&lt;/a&gt; | &lt;a href="https://github.com/HiroItozzz/compose-lazy" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;&lt;/p&gt;

</description>
      <category>cli</category>
      <category>python</category>
      <category>docker</category>
      <category>devops</category>
    </item>
    <item>
      <title>I Published My First Python Package to PyPI — A CLI Tool for Docker Compose</title>
      <dc:creator>HiroItozzz</dc:creator>
      <pubDate>Sun, 03 May 2026 14:49:01 +0000</pubDate>
      <link>https://dev.to/hiroitozzz/i-published-my-first-python-package-to-pypi-a-cli-tool-for-docker-compose-l6o</link>
      <guid>https://dev.to/hiroitozzz/i-published-my-first-python-package-to-pypi-a-cli-tool-for-docker-compose-l6o</guid>
      <description>&lt;h1&gt;
  
  
  I Published My First Python Package to PyPI — A CLI Tool for Docker Compose
&lt;/h1&gt;

&lt;p&gt;I did it. I published my first package to PyPI.&lt;/p&gt;

&lt;p&gt;It's called &lt;strong&gt;fast-dcp&lt;/strong&gt;, and honestly, it started as a personal annoyance. I kept typing &lt;code&gt;docker compose up --build&lt;/code&gt; and &lt;code&gt;docker compose exec app bash&lt;/code&gt; dozens of times a day. My fingers got tired. So I built something about it.&lt;/p&gt;




&lt;h2&gt;
  
  
  What is fast-dcp?
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;fast-dcp&lt;/strong&gt; is a CLI tool that provides shorthand aliases for common &lt;code&gt;docker compose&lt;/code&gt; commands. Nothing revolutionary — just fewer keystrokes for the things you type constantly.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Instead of this:&lt;/span&gt;
docker compose up &lt;span class="nt"&gt;--build&lt;/span&gt;

&lt;span class="c"&gt;# Just type:&lt;/span&gt;
dcpu &lt;span class="nt"&gt;-b&lt;/span&gt;

&lt;span class="c"&gt;# Instead of this:&lt;/span&gt;
docker compose &lt;span class="nb"&gt;exec &lt;/span&gt;app bash

&lt;span class="c"&gt;# Just type:&lt;/span&gt;
dcpe app
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Three commands cover the main workflows:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;dcp&lt;/code&gt;&lt;/strong&gt; — general-purpose wrapper with subcommands (&lt;code&gt;up&lt;/code&gt;, &lt;code&gt;build&lt;/code&gt;, &lt;code&gt;exec&lt;/code&gt;, &lt;code&gt;restart&lt;/code&gt;, &lt;code&gt;ps&lt;/code&gt;, &lt;code&gt;logs&lt;/code&gt;, &lt;code&gt;stop&lt;/code&gt;, &lt;code&gt;down&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;dcpu&lt;/code&gt;&lt;/strong&gt; — dedicated shorthand for &lt;code&gt;docker compose up&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;dcpe&lt;/code&gt;&lt;/strong&gt; — dedicated shorthand for &lt;code&gt;docker compose exec&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Some real examples
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# docker compose up -d&lt;/span&gt;
dcp u &lt;span class="nt"&gt;-d&lt;/span&gt;

&lt;span class="c"&gt;# docker compose -f docker-compose.prod.yml up --build&lt;/span&gt;
dcpu &lt;span class="nt"&gt;-f&lt;/span&gt; docker-compose.prod.yml &lt;span class="nt"&gt;-b&lt;/span&gt;

&lt;span class="c"&gt;# docker compose exec app bash&lt;/span&gt;
dcpe app

&lt;span class="c"&gt;# docker compose exec app uv run pytest&lt;/span&gt;
dcpe app uv run pytest

&lt;span class="c"&gt;# docker compose restart app&lt;/span&gt;
dcp r app

&lt;span class="c"&gt;# docker compose logs app -f&lt;/span&gt;
dcp l app &lt;span class="nt"&gt;-F&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  How it's built
&lt;/h2&gt;

&lt;p&gt;The implementation is pure Python — no external runtime dependencies.&lt;/p&gt;

&lt;p&gt;The core is a &lt;code&gt;DockerCmdProcessor&lt;/code&gt; class that builds up the docker command from parsed arguments and passes it to &lt;code&gt;subprocess.run&lt;/code&gt;. It implements &lt;code&gt;__call__&lt;/code&gt;, so it works naturally as a callable passed to argparse's &lt;code&gt;set_defaults(func=...)&lt;/code&gt; — a pattern recommended in the argparse docs.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="n"&gt;args&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;parser&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;parse_args&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
&lt;span class="n"&gt;code&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;args&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;func&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;args&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="nf"&gt;exit&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;code&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For the CLI definition, I wrote a small &lt;code&gt;ArgDefiner&lt;/code&gt; wrapper around &lt;code&gt;ArgumentParser&lt;/code&gt; to enable method chaining. It made the &lt;code&gt;main()&lt;/code&gt; function much more declarative and readable — inspired by how Django's class-based views compose behavior through mixins.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="nc"&gt;ArgDefiner&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;subparsers&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;add_parser&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;up&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;aliases&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;u&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;],&lt;/span&gt; &lt;span class="p"&gt;...))&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;add_project_args&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;add_file_args&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;add_build_args&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;add_detach_args&lt;/span&gt;&lt;span class="p"&gt;()&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;add_container_name_subcmd&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;multiple&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="bp"&gt;True&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;set_defaults&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;func&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nc"&gt;Processor&lt;/span&gt;&lt;span class="p"&gt;())&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Testing was surprisingly clean. Unit tests cover &lt;code&gt;ArgDefiner&lt;/code&gt; and &lt;code&gt;DockerCmdProcessor&lt;/code&gt; independently, and integration tests use &lt;code&gt;patch("sys.argv", ...)&lt;/code&gt; to simulate real CLI invocations end-to-end.&lt;/p&gt;




&lt;h2&gt;
  
  
  Install it
&lt;/h2&gt;

&lt;p&gt;No external runtime dependencies — pure Python. Just install and use.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="c"&gt;# Using pipx (recommended)&lt;/span&gt;
pipx &lt;span class="nb"&gt;install &lt;/span&gt;fast-dcp

&lt;span class="c"&gt;# Or using uv&lt;/span&gt;
uv tool &lt;span class="nb"&gt;install &lt;/span&gt;fast-dcp
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h3&gt;
  
  
  Not familiar with pipx or uv?
&lt;/h3&gt;

&lt;p&gt;Both install CLI tools in isolated environments — no virtual environment activation needed, no conflicts with other packages. &lt;code&gt;uv tool&lt;/code&gt; is the faster option if you already use uv.&lt;/p&gt;

&lt;p&gt;macOS&lt;/p&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;brew &lt;span class="nb"&gt;install &lt;/span&gt;pipx
pipx ensurepath
pipx &lt;span class="nb"&gt;install &lt;/span&gt;fast-dcp
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;p&gt;Windows&lt;/p&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;python &lt;span class="nt"&gt;-m&lt;/span&gt; pip &lt;span class="nb"&gt;install&lt;/span&gt; &lt;span class="nt"&gt;--user&lt;/span&gt; pipx
python &lt;span class="nt"&gt;-m&lt;/span&gt; pipx ensurepath
&lt;span class="c"&gt;# Restart terminal, then:&lt;/span&gt;
pipx &lt;span class="nb"&gt;install &lt;/span&gt;fast-dcp
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;
&lt;p&gt;Linux (Ubuntu/Debian)&lt;/p&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;pip &lt;span class="nb"&gt;install &lt;/span&gt;pipx
pipx ensurepath
pipx &lt;span class="nb"&gt;install &lt;/span&gt;fast-dcp
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  Requirements
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Python 3.11+&lt;/li&gt;
&lt;li&gt;Docker with Compose V2 (&lt;code&gt;docker compose&lt;/code&gt;, not &lt;code&gt;docker-compose&lt;/code&gt;)&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Honest thoughts on publishing for the first time
&lt;/h2&gt;

&lt;p&gt;This is a small tool. It wraps a handful of docker commands and saves a few keystrokes. But getting it to a point where someone else could &lt;code&gt;pipx install fast-dcp&lt;/code&gt; and have it just work — that took more thought than I expected.&lt;/p&gt;

&lt;p&gt;Packaging, &lt;code&gt;pyproject.toml&lt;/code&gt;, flit, classifiers, editable installs, &lt;code&gt;importlib.metadata&lt;/code&gt;... there's a lot of moving parts for something that feels like it should be simple. I learned a lot just by going through the process.&lt;/p&gt;

&lt;p&gt;If you work with docker compose regularly, give it a try. And if something is broken or missing, feel free to open an issue.&lt;/p&gt;

&lt;p&gt;🔗 &lt;a href="https://pypi.org/project/fast-dcp/" rel="noopener noreferrer"&gt;PyPI&lt;/a&gt; | &lt;a href="https://github.com/HiroItozzz/fast-dcp" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;&lt;/p&gt;

</description>
      <category>docker</category>
      <category>python</category>
      <category>cli</category>
    </item>
  </channel>
</rss>
