// Launches and verifies local dev environments using dockportless with worktree-unique project names. Use when starting docker compose services, checking service accessibility via proxy, enabling TLS/HTTPS routing, or when developing across multiple git worktrees to avoid port collisions.
| name | verifying-dockportless |
| description | Launches and verifies local dev environments using dockportless with worktree-unique project names. Use when starting docker compose services, checking service accessibility via proxy, enabling TLS/HTTPS routing, or when developing across multiple git worktrees to avoid port collisions. |
Use this skill when you need to start a local development environment with docker compose (or compatible tools) via dockportless, and verify that services are accessible. Especially important when developing in parallel across git worktrees on the same machine.
PROJECT_NAME="$(basename "$(git rev-parse --show-toplevel)" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/--*/-/g' | sed 's/^-//;s/-$//')"
Skip this step for HTTP-only services (web apps, REST APIs, etc.).
Run once per machine only when:
sudo dockportless trust
dockportless run "$PROJECT_NAME" docker compose up -d
Each service is available at <service>.<project_name>.localhost:7355:
curl http://web.$PROJECT_NAME.localhost:7355/
# Check HTTP response
curl -s -o /dev/null -w '%{http_code}' http://web.$PROJECT_NAME.localhost:7355/
dockportless stores port mappings per project name internally. If two worktrees use the same project name, one overwrites the other's mapping and proxy routing breaks.
Derivation strategy: Use the worktree directory basename, which is guaranteed unique on the filesystem.
/home/user/myapp -> project_name: "myapp"
/home/user/myapp-feat-login -> project_name: "myapp-feat-login"
/home/user/myapp-fix-auth -> project_name: "myapp-fix-auth"
Each gets its own allocated ports and its own proxy routes.
Services must use ${SERVICE_PORT:-default} pattern in ports. See COMPOSE-SETUP.md for single-port, multi-port examples, and env var naming rules.
dockportless trust)Not needed for HTTP-only services. Required only for HTTPS, PostgreSQL, Redis, or MongoDB direct access. See TLS-ROUTING.md for protocol details, decision table, and client examples.
sudo dockportless trust — only for HTTPS, PostgreSQL, Redis, MongoDB accessdockportless run "$PROJECT_NAME" <compose-command><service>.$PROJECT_NAME.localhost:7355docker compose down (dockportless cleans up mapping on exit)