mickamy

mickamy / tug

Public

Replace port conflicts with stable, named URLs for Docker Compose.

13
2
100% credibility
Found Feb 28, 2026 at 11 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
Go
AI Summary

Tug is a tool that enhances local app development by automatically providing unique web addresses for web services and stable connection points for data services across multiple projects to avoid conflicts.

How It Works

1
😩 Hit port conflicts

You try running several apps on your computer at once, but they fight over the same connection spots, forcing you to stop and restart constantly.

2
🔍 Discover tug

You learn about tug, a handy helper that lets multiple apps run together peacefully by giving each its own special web addresses and steady spots.

3
📦 Set up tug

Pick an easy way to add tug to your computer, like grabbing a ready-to-use file or using a simple installer.

4
🚀 Start your app

In your project folder, launch everything with tug – it smartly assigns friendly web links to your web parts and reliable spots to your data keepers, no clashes.

5
📋 View your links

Check the list to see custom web addresses like yourservice.yourapp.local and exact connection spots for each part, all running smoothly.

6
🔄 Add more apps

Repeat in another project folder – tug keeps everything separate and happy, so all your apps live side by side.

🎉 Develop freely

Now juggle multiple projects effortlessly, testing and building without ever worrying about connection fights again.

Sign up to see the full architecture

5 more

Sign Up Free

Star Growth

See how this repo grew from 11 to 13 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is tug?

Tug is a Go CLI that wraps Docker Compose (or Podman) to eliminate port conflicts across multiple projects or git worktrees. Run `tug up` and it auto-assigns stable `http://..localhost` URLs for HTTP services via a shared Traefik proxy, while hashing project+service names to give TCP services like Postgres or Redis consistent host ports in the 10000-60000 range. Other commands like `tug ps` show endpoints, and everything else passes through to `docker compose`.

Why is it gaining traction?

Unlike manual port juggling or tools like Portainer, tug delivers zero-config routing that just works for multi-project workflows—perfect for replacing port conflicts without changing compose files. Deterministic ports mean the same setup yields identical localhost mappings across machines or restarts, and `tug ps --json` enables scripting. Git worktree fans get seamless parallelism without stopping services.

Who should use this?

Backend devs managing microservices stacks with shared DBs across branches or worktrees. Teams running parallel compose projects locally, tired of editing ports in recipes or chasing conflicts. Anyone replacing Portainer with a lightweight CLI for HTTP/TCP routing in Docker Compose setups.

Verdict

Try tug if port conflicts kill your flow—it's a smart, tested niche tool with solid docs and Podman support, but at 11 stars and 1.0% credibility, it's early-stage; watch for broader adoption before production reliance.

(187 words)

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.