tailscale-manager

Expose Docker containers to the internet by managing Tailscale funnels, which route external traffic to local container ports. This Skill automates funnel lifecycle management—start, stop, and verify status—while enforcing the constraint that only one funnel can run on port 443 at a time across your ct projects.

Yes, you can route traffic to multiple ct project containers using port mapping strategy. Each ct project follows consistent port patterns—API on 808X, Database on 543X, Redis on 637X—and the Skill manages switching between ports safely while maintaining the single active funnel per instance rule.

Start a funnel in background mode for your specific ct project, then verify status. Background mode runs persistently across reboots and terminal sessions, supporting production use cases, while foreground mode provides ephemeral funnels for temporary testing scenarios.

Use consistent ct project port patterns: API services on 808X ports, Database services on 543X ports, and Redis services on 637X ports. The Skill enforces these patterns and manages traffic routing to the appropriate container port automatically.

Yes, this Skill applies across multiple ct projects with consistent port patterns and lifecycle behavior. It maintains the single active funnel constraint per instance and supports both ephemeral and persistent modes, ensuring safe port switching and status verification across all projects.

Background mode funnels maintain lifecycle behavior across reboots and terminal sessions for persistent routing. Foreground mode funnels are ephemeral and terminate with the session, allowing you to choose persistence based on your testing or production needs.