Worktree Manager

Manages Docker app instances and git worktrees for local development.

Each instance gets its own docker-compose stack (backend + frontend), isolated git branch, and .env.worktree-\x3Cname> file. MySQL and nginx-proxy are managed separately by their own plugins.

Prerequisites

Start these first (order matters):

1. proxy-manager start — creates the shared Docker network (nginx-proxy_net)
2. mysql-manager start — starts the shared MySQL container

Architecture

project/
├── docker-compose.yml        # app stack template (backend + frontend)
├── run.sh                    # this plugin's entry point (copy to project root)
├── .env.base                 # main instance env
├── .env.worktree-\x3Cname>      # per-worktree env (gitignored)
└── .worktrees/
    └── \x3Cname>/               # git worktree (gitignored)

• main → .env.base, project root
• worktree → .env.worktree-\x3Cname>, checked out at .worktrees/\x3Cname>
• URLs: http://\x3Cname>.frontend.localhost / http://\x3Cname>.backend.localhost

Commands

All commands run from the project root:

./run.sh list                        # show all instances + mysql/proxy status
./run.sh start [main|\x3Cname>]         # seed db, start containers, connect proxy
./run.sh stop  [main|\x3Cname>]         # stop containers (db persists)
./run.sh restart [main|\x3Cname>]       # stop then start
./run.sh logs  [main|\x3Cname>]         # follow container logs
./run.sh create-worktree \x3Cname>      # git worktree + branch + env file
./run.sh remove-worktree \x3Cname>      # stop containers + drop db + remove worktree

How to Execute Tasks

Full environment setup (first time)

proxy-manager/run.sh start        # network + nginx-proxy
mysql-manager/run.sh start        # MySQL
./run.sh start main               # main app instance

Create a new worktree and start it

1. ./run.sh create-worktree \x3Cname> — creates branch worktree/\x3Cname>, dir .worktrees/\x3Cname>, env file
2. ./run.sh start \x3Cname> — seeds db from main snapshot, starts containers, activates proxy route
3. URLs reported at the end

Stop an instance

./run.sh stop \x3Cname>

Remove a worktree (destructive — always confirm first)

Confirm with user: "Remove worktree '\x3Cname>'? Deletes containers, database, git worktree (branch worktree/\x3Cname>), and .env.worktree-\x3Cname>."

./run.sh remove-worktree \x3Cname>

List all instances

./run.sh list

What start Does

1. Checks MySQL container is running (exits with error if not)
2. CREATE DATABASE IF NOT EXISTS for the instance
3. For non-main instances: dumps codai_main → instance db
4. docker compose up --build -d
5. docker network connect — proxy to instance network (activates routes)

Rules

• Always check ./run.sh list before starting — it shows MySQL/proxy status.
• Always confirm before remove-worktree — it is irreversible.
• After start, print the frontend and backend URLs.
• If ./run.sh is not executable: chmod +x run.sh
• .env.worktree-* files and .worktrees/ dir must be gitignored.

Configuration

Related Plugins

• proxy-manager — nginx-proxy lifecycle and network management (start first)
• mysql-manager — MySQL lifecycle and database admin (start second)