ambit-cli
por toxicpine
DevOps & CloudResumen
Use this skill for any task involving the ambit CLI: creating or destroying private networks, deploying apps.
Descripción
Qué hace esta skill
Ambit deploys apps to Fly.io inside a private Tailscale network, making them unreachable from the public internet. Only devices enrolled in the user's Tailscale network can connect to deployed apps. Access control is enforced at the network level, so apps need no login pages or firewall rules.
Enforces access at the network layer instead of the application layer, so internal tools are private by default without any app-level hardening.
Cuándo usarla
- Deploying an internal dashboard without a public IP
- Running a headless browser accessible only to team devices
- Hosting a private dev shell reachable from any enrolled device
- Deploying a database or admin tool without configuring firewalls
- Sharing internal tools with teammates by enrolling their devices in the tailnet
Flujo de trabajo de ejemplo
User asks: Deploy a headless Chrome browser to my private lab network
- 1
Runs
ambit create lab --self-approveto provision a Fly.io router joined to the Tailscale network - 2
Runs
ambit deploy my-browser --network lab --template ToxicPine/ambit-templates/chromaticto fetch and deploy the headless Chrome template - 3
Runs
ambit status --network labto confirm the router and app are online - 4
Confirms the app is accessible at my-browser.lab:9222 from any enrolled device
Headless Chrome is running at my-browser.lab:9222, reachable only from devices enrolled in the Tailscale network
Requisitos
- Fly.io account with flyctl installed and authenticated
- Tailscale account with the app installed and connected
- Tailscale API access token (tskey-api-...) from login.tailscale.com/admin/settings/keys
Instalación
clawhub install toxicpine/ambit-cliEjecuta el comando de la CLI o pega el prompt en Claude Code, Cursor, Codex o el agente de programación que uses.