DeployCLI Reference
eda tunnel
Automated public HTTPS tunnel forwarding for deployed containers without DNS configuration
The eda tunnel command group provisions and manages automated public HTTPS reverse tunnels (*.tunnel.explita.ng) for your remote container applications. It bridges Explita Deploy with Explita Tunnel, enabling instant worldwide internet reachability without requiring custom domains or DNS records.
eda tunnel <subcommand> [options]
explita deploy tunnel <subcommand> [options]1. Subcommands Overview
| Command | Description |
|---|---|
eda tunnel enable | Provision and activate an encrypted public HTTPS tunnel for the application. |
eda tunnel disable | Terminate the public tunnel while keeping the container running. |
2. Enable Automated Public Tunnel (eda tunnel enable)
Request an encrypted edge ingress tunnel for your container:
eda tunnel enable [-a <appId>] [-s <subdomain>]Options
| Flag | Shorthand | Type | Description |
|---|---|---|---|
--app <appId> | -a | String | Target application ID (defaults to local explita.json). |
--subdomain <prefix> | -s | String | Request a specific custom subdomain prefix. |
Examples:
# Enable tunnel with auto-generated subdomain
eda tunnel enable
# Enable tunnel with a custom subdomain prefix
eda tunnel enable -s payment-apiOutput:
✔ Tunnel enabled for application app_9f3a12.
Tunnel URL: https://payment-api.tunnel.explita.ngKey Use Cases:
- Instant Webhook Testing: Provide a public HTTPS endpoint to Stripe, GitHub, Twilio, or Shopify immediately after deployment.
- Client Previews: Share live feature builds with clients or stakeholders before purchasing or configuring custom domain names.
- Zero-Config Staging: Test microservices in staging environments without modifying internal VPC DNS routes.
3. Disable Public Tunnel (eda tunnel disable)
Close the edge reverse tunnel when external testing is complete:
eda tunnel disable [-a <appId>]Example:
eda tunnel disableThe public tunnel URL is immediately invalidated at the edge gateway. Your internal application container continues running unaffected on its local host port and internal network bridge.